Skip to content

add new generic easyblock for installing a bundle of modules#550

Merged
boegel merged 2 commits intoeasybuilders:developfrom
boegel:bundle
Feb 6, 2015
Merged

add new generic easyblock for installing a bundle of modules#550
boegel merged 2 commits intoeasybuilders:developfrom
boegel:bundle

Conversation

@boegel
Copy link
Copy Markdown
Member

@boegel boegel commented Feb 5, 2015

this has been talked over a lot, but never got looked into

Bundle should be used for anything that's just a (drumroll) bundle of modules, without any additional meaning; examples include the HPCBIOS bundles (e.g., https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs/h/HPCBIOS_LifeSciences); @fgeorgatos: up for tackling that once this gets merged?

toolchains should still use the Toolchain which is now reworked on top of Bundle, since it does have additional meaning and I expect the Toolchain generic easyblock to do more than just bundle things together in the feature (e.g. potentially defining things like $CC, etc., probably with pushenv)

@hpcugentbot
Copy link
Copy Markdown

Refer to this link for build results (access rights to CI server needed):
https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/767/
Test PASSed.

@hpcugentbot
Copy link
Copy Markdown

Refer to this link for build results (access rights to CI server needed):
https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/768/
Test PASSed.

@boegel
Copy link
Copy Markdown
Member Author

boegel commented Feb 5, 2015

@wpoely86: please review?

@wpoely86
Copy link
Copy Markdown
Member

wpoely86 commented Feb 6, 2015

looks great

@boegel
Copy link
Copy Markdown
Member Author

boegel commented Feb 6, 2015

Thanks for the review @wpoely86!

boegel added a commit that referenced this pull request Feb 6, 2015
add new generic easyblock for installing a bundle of modules
@boegel boegel merged commit 89a4d8a into easybuilders:develop Feb 6, 2015
@boegel boegel deleted the bundle branch February 6, 2015 20:33
@fgeorgatos
Copy link
Copy Markdown
Contributor

Just for the record, here are 3 different use-cases that may look as apparent "bundles" yet different each:

  • HPCBIOS_LifeSciences: these should rely on a single toolchain; $CC and co unneeded though
  • HPCBIOS_Debuggers: these should NOT rely on any toolchain, ideally should be static builds
  • PRACE: this actually may remain a genuine toolchain; it is a bit "fat" stack, yet there is meaning to it.

I recommended to use the 8th hackathon to discuss the different use-cases and understand the merits of possible choices. IMHO, a bundle that does no builds is a whole new case than the above ;-)

@boegel
Copy link
Copy Markdown
Member Author

boegel commented Feb 7, 2015

It doesn't really matter for a bundle whether it requires a particular toolchain (dummy or otherwise).

The point is that this is just a group of modules, nothing more. A toolchain is a very particular sort of group of modules, but as far as just installing the toolchain module itself is concerned, there's nothing really special about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants