As discussed in the recent maintainer summit, it would be very useful to introduce a feature that can make it easier to figure out which easyconfigs have changed, without needing to trawl through release notes. In particular:
- easyconfigs that have changed between the most recent EB releases (maybe look for
bugfix and change labels?)
- potentially filtered against installed easyconfigs in a particular prefix?
- @Flamefire suggests looking into GitHub GraphQL
- also consider easyblocks
- comparing an installed easyconfig against the first match in the robot path
- diff
<installdir>/easybuild/<easyconfig> against robot path match
- could check what ec parameters changed (e.g. new patch, modified configopts, etc)
- similarly for easyblocks/hooks
- could do this recursively (for the easyconfig, or whole software tree)
In any case, I think it's useful to have both a reporting mode (human-readable), and a mode that spits out a list of easyconfigs (maybe integrated with --rebuild if you feel adventurous).
As discussed in the recent maintainer summit, it would be very useful to introduce a feature that can make it easier to figure out which easyconfigs have changed, without needing to trawl through release notes. In particular:
bugfixandchangelabels?)<installdir>/easybuild/<easyconfig>against robot path matchIn any case, I think it's useful to have both a reporting mode (human-readable), and a mode that spits out a list of easyconfigs (maybe integrated with
--rebuildif you feel adventurous).