After being bitten by wrong file permissions in G4EMLOW (I only found a substitute file for 6.32, I didn't see it for 6.23 - not that it matters, I fixed it manually), I checked all other permissions as well. Even though no other file is strictly problematic, the files below could have had different permissions. Most versions are outdated by now and permissions are fixed in newer versions, but G4NEUTRONSX1.3 is the latest version. ./G4NEUTRONXS1.1: -rwxr-xr-x 1 macports admin 256B 15 nov 2011 History -rwxr-xr-x 1 macports admin 428B 15 nov 2011 README ./G4NEUTRONXS1.2: -rwxr-xr-x 1 macports admin 331B 15 okt 2012 History ./G4NEUTRONXS1.3: -rwxr-xr-x 1 macports admin 406B 8 feb 20:44 History -rwxr-xr-x 1 macports admin 547B 8 feb 20:43 README ./PhotonEvaporation2.2: -rwxr-xr-x 1 macports admin 210B 2 dec 2011 History -rw-r----- 1 macports admin 2,3K 2 dec 2011 z6.a12 -rw-r----- 1 macports admin 2,3K 2 dec 2011 z6.a13 -rw-r----- 1 macports admin 1,9K 2 dec 2011 z6.a14 -rw-r----- 1 macports admin 165B 2 dec 2011 z6.a15 -rw-r----- 1 macports admin 11K 2 dec 2011 z92.a232 -rw-r----- 1 macports admin 9,5K 2 dec 2011 z92.a233 -rw-r----- 1 macports admin 72K 2 dec 2011 z92.a234 -rw-r----- 1 macports admin 37K 2 dec 2011 z92.a235 -rw-r----- 1 macports admin 23K 2 dec 2011 z92.a236 -rw-r----- 1 macports admin 13K 2 dec 2011 z92.a237 -rw-r----- 1 macports admin 30K 2 dec 2011 z92.a238
We have changed the procedure to include a check for bad permissions before creating the tar file. The latest data set for G4EMLOW, G4EMLOW6.33 should have correct permissions. As you noted, there is a corrected files for 6.32, but as CMake checks a md5sum, we cannot replace the original file. Note that we will not correct the old set G4EMLOW6.23. G4NEUTRONXS has the eXecute bit set on README and History. , We will fix this for future versions, but not for the released versions, since the consequences of teh execute bit are minimal.
Thank you. Of course I didn't expect you to fix anything with respect to the released files. Just making sure that the future versions/releases will be ok.