-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
animbar: init at 1.2 #44608
animbar: init at 1.2 #44608
Conversation
|
||
nativeBuildInputs = [ cmake ]; | ||
|
||
buildInputs = [ qt4 file ]; |
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.
Have you tried to build this with qt5? We are trying to get rid of qt4 in nixpkgs, see #33248 .
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.
Yes, I have tried. It fails to build without qt4.
Regarding removal of qt4: I've not involved with the discussion so far, but I'm in the camp of @vcunat of peaceful coexistence. I see no point in removing an entire toolkit from Nixpkgs 'just because you can'. Like in the case of this software: I'm not aware of a real equivalent. It does its (simple but unique) job. And it is uncertain whether it will ever be changed to some new version of Qt - what need would there be.
qt4 stands for a decade of free software history. If you don't have any software that uses qt4 installed, it does not burden you. And if you want to use it, you are willing to pay the 'price' of extra storage. Of course, in case of software that can be built with both there is no need to have two versions - and moving those to "qt5 exclusive" is a sane thing to optimise the common experience.... but removal isn't necessary.
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.
Yes, I have tried. It fails to build without qt4.
Fine, that's all I wanted to know. My opionion on the general issue is that, if a package supports both qt4 and qt5, we should prefer qt5. But there's no reason to refuse packages that need qt4.
@GrahamcOfBorg build animbar |
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: animbar Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: animbar Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: animbar Partial log (click to expand)
|
timeout building qt ... unrelated. |
I tried porting it to Qt5 and sent the patch to authors jtojnar/animbar@1ae854e |
@jtojnar: Great! Hope they respond. meanwhile we could add a patchPhase, with your patch: |
Motivation for this change
Unusual animation tool that can be used to create physical animations.
Things done
sandbox
innix.conf
on non-NixOS)./result/bin/
)