#32716: geant4: update to 9.5 -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: cristiano.fontana@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: geant4 -------------------------------------+-------------------------------------- Comment(by mojca.miklavec.lists@…): I believe that the data being fetched is checksummed as well (I already got some warnings/errors about wrong checksums): {{{ # Where to install data in the install tree (a Default) set(GEANT4_INSTALL_DATADIR_DEFAULT "${CMAKE_INSTALL_DATAROOTDIR}/${PROJECT_NAME}-${${PROJECT_NAME}_VERSION}/data") # Define the known datasets as a list of tuples, tuple entries being # forward slash separated. Messy. # Tuple entries: # 0 : Directory Name # 1 : Version # 2 : Filename # 3 : Filename Extension # 4 : Environment Variable # 5 : Expected MD5 sum File # 6 : (NOTIMPLEMENTEDYET) Marker for detecting existing install # set(GEANT4_DATASETS G4NDL/4.1/G4NDL/tar.gz/G4NEUTRONHPDATA/ff018eca2c2ca3bc32a096c2d72df64f G4EMLOW/6.27/G4EMLOW/tar.gz/G4LEDATA/4d204b9d730148d3e34b490105aed1bd PhotonEvaporation/2.2/G4PhotonEvaporation/tar.gz/G4LEVELGAMMADATA/8010e7ce8a92564e38dd3418e6040563 RadioactiveDecay/3.4/G4RadioactiveDecay/tar.gz/G4RADIOACTIVEDATA/a5b681048584631608ab0965b33c7959 G4ABLA/3.0/G4ABLA/tar.gz/G4ABLADATA/d7049166ef74a592cb97df0ed4b757bd G4NEUTRONXS/1.1/G4NEUTRONXS/tar.gz/G4NEUTRONXSDATA/61ef3a05b56525db04e11820e3f603f1 G4PII/1.3/G4PII/tar.gz/G4PIIDATA/05f2471dbcdf1a2b17cbff84e8e83b37 RealSurface/1.0/RealSurface/tar.gz/G4REALSURFACEDATA/0dde95e00fcd3bcd745804f870bb6884 ) }}} but of course doing the download automatically puts it slightly out of MacPorts' control. Of course, "manual/separate" download (like it has always been done for Geant4) is always possible. One argument might also be that "port clean geant4" would probably delete data files if fetched during installation, while if they are fetched during download, they stay on machine and may be reused. (However I won't buy the argument that the packager is actually testing the contents of those files :) My suggestion would be to create geant4-devel with 4.9.6 beta (or 4.9.5) when switching to CMake files since the installation can make quite a difference depending on user's habits. That would enable wider testing audience for a longer period of time. Saying that "Geant4 works" is namely not too well defined, in particular because different users use different approaches to find Geant4 (GNUmakefile, CMake, manual compilation, ...), most of them using DYLD_LIBRARY_PATH which makes my programs crash etc. -- Ticket URL: <https://trac.macports.org/ticket/32716#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS