On 04 Nov 2013, at 20:49, Fotis Georgatos wrote: > > Hi Ward, *, > > On Nov 4, 2013, at 8:15 PM, Ward Poelmans wrote: >>> * module statistics! # how to record module usage; what do you do? >> >> Is this something for EB? I would think it's more something to >> implement in lmod? > > It is more of a survey to fellows about what they do, so that we can do some > shopping; > I found out that TACC checks env during shell logout, while UGhent rewires > module() cmd.
Again, let's keep this out of the EB conf call, it's out-of-scope, and will only steal time of other topics. Open a separate mail thread on this to the EB mailing list if you want, and collect documented approaches on a wiki page to be added to the EasyBuild wiki. We collect info by making module loads to be logged to syslog, but haven't done anything with that data yet, we just have it around. > >>> * Inform upstream developers of patch effort, add REF. with tracking URL >>> within patch files >> >> +1, I usually push patches upstream but something to add tracking >> would be useful. > > Indeed, eventually we would all benefit more by showing to the upstream > developers, > any hacks we need to apply to get things done - for an HPC service; in my > experience, > most care about it and will eventually fix it or, provide hooks to avoid > patching. My experience is different (i.e. people are reluctant to include patches that fix their code for building with Intel compilers because they only care about GCC), but that doesn't mean we shouldn't try and push patches upstream. I personally don't have time to follow up on it, so I end up not pushing them back (sadly). K.
