Hi Andreas,
On 05/05/2017 08:16, Henkel, Andreas wrote:
Hi,
@Jens: Thank you very much for your detailed reply. I really appreciate it.
Personally, I don't have a problem with all the easybuild packages since they
are not opening up for root. I rather appreciate that users could built up
their own eb on out clusterwide installation. And the time saving for
installation is great (except if you make a bad choice and choose foss-2017a as
default tool chain but now I know much more about eb because of all the
modifications I had to make ;-) )
There was another interesting point raised about update cycles: what if
something is misconfigured in the easyconfigs for blas for example which would
lead to wrong results for the users using that lib? I know that this is not
directly related to easybuild but wanted to ask anyway...
About the update checker @Damian pointed to a related pull request (thank
you!). Do I get it right that there is no such thing as checking for newer
versions of installed software? The point why I'm asking is just because I'm
thinking about diving into this. Thinking about something similar to apt update
which simply lists available upgrades. Actually, we have some python-code that
does this for our installed modules and sends its results to nagios/icinga.
This would be more of an update notifier and don't do any action. If there
isn't something like that yet I can have a look how to adapt our stuff to eb.
Any pointer to a good place in the framework is appreciated.
We have plans to leverage Anitya [1] to let EasyBuild query for
available versions of a particular software packages.
The idea would be that you could easily install the latest version of a
particular software package, where EasyBuild figures out what the latest
version is for you.
For now, this is just an idea though.
If you're up for diving into this, we can discuss this further (e.g. via
a conf call).
regards,
Kenneth
[1] https://github.com/release-monitoring/anitya
