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

Checking compiler version constraints #56

Open
Pawe1 opened this issue Oct 9, 2017 · 3 comments
Open

Checking compiler version constraints #56

Pawe1 opened this issue Oct 9, 2017 · 3 comments

Comments

@Pawe1
Copy link
Contributor

Pawe1 commented Oct 9, 2017

When user tries to install package with package_compiler_min / package_compiler_max / compiler_min / compiler_max values set that doesn't meet host IDE version there should be at least warning message.

Currently it is possible to install 10.2 only packages on for example XE 7.

@Memnarch
Copy link
Owner

yup. STill haven't fixed that :/. Idea was to add filtering an simulate a given compilerversion when forcing it. (For example if lowest compiler-version is berlin and you use XE8, the script will run the Berlin-Nodes)

@rlebeau
Copy link

rlebeau commented Aug 23, 2018

I thought the whole purpose of (package_)compiler_... was to prevent this kind of thing from happening? If the min/max is set to 10.2, then the package shouldn't be made available to XE7 at all. Am I wrong?

@Memnarch
Copy link
Owner

That is correct. Just had not added a filter to the UI (though it shows the versions it applies to). I should go through all my issues here and work on them again (and way to much to do otherwhise)

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

No branches or pull requests

3 participants