-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Add a noqt package and variants noqt5, noqt6 #25688
Conversation
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/noqt:
|
recipes/noqt/meta.yaml
Outdated
# qt-main is essentially qt5 | ||
- qt-main <0.a0 | ||
# before the creation of qt-main, a megapackage called qt existed | ||
- qt <0.a0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be loosened to qt <5.a0
to allow for qt4 to be installed? i feel like that will cause a whole set of other problems.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly, hence why I think the distinction between noqt5
and noqt4
isn't worth it.
For some odd reason I missed this ping. I'm OK with it. I don't see any obvious downsides. |
Hi friend! We really, really, really appreciate that you have taken the time to make a PR on In an effort to maintain this repository and increase the signal-to-noise for open PRs, the maintainers of If you'd like to keep it open, please comment/push and we will be happy to oblige! Note that very old PRs will likely need to be rebased on Cheers and thank you for contributing to this community effort! |
Hi! This is the staged-recipes linter and I found some lint. File-specific lints and/or hints:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
I've reopened this because it seems like it may help at compilation to resolve environments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for coming up with this! I think the idea is great, and it would be great to have for certain build scenarios! Some comments below.
recipes/noqt/meta.yaml
Outdated
build: | ||
noarch: generic | ||
requirements: | ||
run_constrained: | ||
# qt4 only ever had a "mega qt" package called qt | ||
- qt <0.a0|>=5.a0 | ||
test: | ||
commands: | ||
- echo "no tests for this package" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would skip noqt4
completely. qt4 is so old (the last build was >5 years ago) that it's essentially uninstallable anyway.
With noqt5
requiring both qt <0.0a0
and qt-main <0.0a0
, that already encompasses all remnants of qt4 that might exist.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok. i removed noqt4
.
recipes/noqt/meta.yaml
Outdated
# qt-main is essentially qt5 | ||
- qt-main <0.a0 | ||
# before the creation of qt-main, a megapackage called qt existed | ||
- qt <0.a0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need a minor version before the "a0". Also, I would only do qt-main <5.0a0
, so we don't close the door that qt6-main
eventually becomes qt-main
. That the output got renamed was to enable co-installation; once qt5 fades away, we won't need that anymore. Not saying that's a good enough reason to then change it, but it might happen.
# qt-main is essentially qt5 | |
- qt-main <0.a0 | |
# before the creation of qt-main, a megapackage called qt existed | |
- qt <0.a0 | |
# qt-main only exists as of 5.x | |
- qt-main <5.0a0 | |
# before the creation of qt-main, a megapackage called qt existed | |
- qt <0.0a0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks o hope i addressed the 2 points.
recipes/noqt/meta.yaml
Outdated
run_constrained: | ||
# For qt6, we always had qt6-main | ||
- qt6-main <0.a0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
run_constrained: | |
# For qt6, we always had qt6-main | |
- qt6-main <0.a0 | |
run_constrained: | |
# For qt6, we always had qt6-main | |
- qt6-main <0.0a0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thnaks.
recipes/noqt/meta.yaml
Outdated
# qt-main is essentially qt5 | ||
- qt-main <0.a0 | ||
# before the creation of qt-main, a megapackage called qt existed | ||
- qt <0.a0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly, hence why I think the distinction between noqt5
and noqt4
isn't worth it.
What do you mean here? Like if the structure of the qt packages changes, we need to modify the repodata? I think that's an acceptable price if we end up doing big changes (which would have to be well-justified in and of themselves anyway). |
I mostly mean helping to reduce the scope of this. For now, that means removing the |
recipes/noqt/meta.yaml
Outdated
# qt-main only exists as of 5.x | ||
- qt-main <0.0a0 | ||
- qt-main <5.0a0|>=6.0a0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remember some discussion in mamba recently about these kind of "or" specifiers. Can we get confirmation that they're fully supported in mamba (@jjerphan @JohanMabille) & pixi (@wolfv @baszalmstra)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The |
operator is supported by mamba.
For instance see this test out of many more in the same file.
IIRC, the discussion were around another MatchSpec
, namely openblas 0.2.18|0.2.18.*.
for which the trailing *.
segment is not properly supported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fully supported by rattler/py-rattler/pixi/rattler-build as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
I think we're good to merge here? |
yes, feel free to press merge, but i don't think it resolves your main concern. (more info on the original feedstock that brought us here) |
See conda-forge/opencv-feedstock#293 and more recent interest: conda-forge#25669 @conda-forge/qt-main requests for comments and thoughts is greatly appreciated @ocefpaf one of my concerns was about "maintainability" of this package. It seems that the only way to update such a package is through repodata patches. As such, I decided to create out of an abundance of caution a noqt4 package. Let me know what you think.
Co-authored-by: h-vetinari <h.vetinari@gmx.com>
Co-authored-by: h-vetinari <h.vetinari@gmx.com>
Co-authored-by: h-vetinari <h.vetinari@gmx.com>
I think this can at least help CIs avoid a qt download. users can add "noqt" to help the solving from finding qt. |
See conda-forge/opencv-feedstock#293 and more recent interest: #25669
@conda-forge/qt-main requests for comments and thoughts is greatly appreciated
@ocefpaf one of my concerns was about "maintainability" of this package. It seems that the only way to update such a package is through repodata patches. As such, I decided to create out of an abundance of caution a noqt4 package. Let me know what you think.
cc: @traversaro @jschueller
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).