Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BinariesTarball inherits unused extra_options from Tarball #2890

Open
VRehnberg opened this issue Feb 15, 2023 · 1 comment
Open

BinariesTarball inherits unused extra_options from Tarball #2890

VRehnberg opened this issue Feb 15, 2023 · 1 comment
Milestone

Comments

@VRehnberg
Copy link
Contributor

The Tarball EasyBlock defines two extra_options install_type and preinstall_cmd. Besides a log message in run, the only place both are used is in the install_step.

So far it is perfectly fine. However, the BinariesTarball inherits the extra_options but overrides the install_step. Thus, the extra_options inherited from Tarball does nothing when used with BinariesTarball.

This behaviour was confusing to me as that is not what is stated in the documentation.

I see two possible solutions:

  1. Rewrite the easyblocks such that BinariesTarball uses the extra_options.
    2 .Override extra_options in BinariesTarball to remove unused extra_options.

As I found this issue when I was trying use preinstall_cmd I would prefer 1. If you agree that this is a bug I could probably write up a PR.

@jfgrimm jfgrimm added this to the 4.x milestone Feb 15, 2023
@smoors
Copy link
Contributor

smoors commented Mar 3, 2023

i agree it's a bug

would be good to reorganize Tarball a bit into so that the logic around install_type and preinstall_cmd doesn't have to be duplicated in BinariesTarball

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

No branches or pull requests

3 participants