Skip to content

add support for 'exts_default_options' easyconfig parameter#2345

Merged
wpoely86 merged 2 commits intoeasybuilders:developfrom
boegel:ext_default_options
Nov 17, 2017
Merged

add support for 'exts_default_options' easyconfig parameter#2345
wpoely86 merged 2 commits intoeasybuilders:developfrom
boegel:ext_default_options

Conversation

@boegel
Copy link
Copy Markdown
Member

@boegel boegel commented Nov 16, 2017

We currently use something like this in some easyconfig that have a long list of extensions (e.g. R):

ext_options = { ... }

exts_list = [
    ('<name1>', '<version1>', ext_options),
    ...,
]

(where ext_options is just a local variable in the easyconfig file, EasyBuild itself ignores it when parsing)

In places where we need to list additional options, we do ugly things like:

    ('<name2>', '<version2>', dict(ext_options.items() + [('patches', ['example.patch'])])),

This change adds support for exts_default_options, which cleans up this mess thoroughly, as follows:

exts_default_options = { ... }

exts_lists = [
    ('<name1>', '<version1>'),
    ('<name2>', '<version2>', {
        'patches': ['example.patch'],
    }),

This is particularly useful when we want to enforce having checksums for all extensions...

@boegel boegel added this to the 3.5.0 milestone Nov 16, 2017
'toolchain = {"name": "dummy", "version": "dummy"}',
'exts_default_options = {',
' "source_tmpl": "gzip-1.4.eb",', # dummy source template to avoid downloading fail
' "source_urls": ["http://example.com/"]',
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add something with a %(...)s too?

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants