Hi, On Jan 19, 2016, at 7:53 AM, Kenneth Hoste <[email protected]> wrote: > Switching to an all-lowercase policy for software names is an intrusive > change though, but maybe worth considering. > It's kind of a religious discussion though, there's no "right" option here > imho...
Indeed. IMHO, maximising the number of symbols for defining packages is advantageous, to prevent name collisions at the level of the easyconfigs. You may find it charming how many “Charm”s there are - pun intended. On the latter case, dependency resolution from a standard tree could prove quite a challenge. So, having said that I’m leaning in favour of maintaing the current status quo, as regards easyconfig sources. That being said, I can see why some sites would prefer to to turn all modulefiles into lowercase - no problem with that; `module load r` might appear a bit weird but fine. And Lmod case insensitivity would help this, too. Let’s not forget at this point that there *IS* potential collision at run-time, due to vars, say EBROOTCHARM… (although I haven’t met or figured any useful combination of software which could make this an issue). best, Fotis -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # signal detected in a CERN forum
