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
gimp: Testing dev version with Meson #67576
base: master
Are you sure you want to change the base?
Conversation
The gjs failure will require #72805 |
]; | ||
|
||
buildInputs = [ | ||
python3 |
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.
Think this won't work if it ends up in a shebang for darwin (because wrappers).
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.
Bah. Hoping for C wrappers before GIMP 3 is released.
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.
Good news! makeBinaryWrapper
is a thing now: #124556
715ab15
to
f52c409
Compare
c750da1
to
359513f
Compare
@GrahamcOfBorg eval |
d83954d
to
65d90f9
Compare
Because it is still unstable and managing multiple expressions for each package variant is pain. |
Is it that painful, really? We would still be moving to this derivation when (eventually) it releases. If no major changes in build system are expected, I think that merging this as |
Yes. We already experienced this with Glimpse GIMP fork. Given that it is trivial to use packages from separate branches in Nix, I do not think the downsides are worth it. |
Rebased but cannot update further due to libjxl 0.7 being stuck in darwin hell #205270 (comment) |
There's a workaround now, so it builds everywhere. |
Co-Authored-By: Linus Heckemann <git@sphalerite.org>
https://www.gimp.org/news/2022/08/27/gimp-2-99-12-released/ GNOME/gimp@256b2d9...a791151 Introduces `gimp-script-fu-interpreter-3.0` as interpreter invoked by shebang of some plug-ins. Let’s ensure it is on `PATH`.
GNOME GitLab instance fails with “fatal: the remote end hung up unexpectedly”
GNOME/gimp@a791151...ad7a2e5 Adds OpenMP support.
Can we maybe just remove the old GIMP? I know 3.0 isn't released, but it seems better than the old one in every respect at the state it currently is. |
Gimp 2.99 crashes for me without
|
Any progress ? |
How can one build this properly? I've tried several commits on this thread, and they call come back with something like
|
Update for 2.99.16: https://git.sr.ht/~fd/nix-configs/tree/main/item/pkgs/gimp-devel/default.nix |
Given that GIMP is finalizing their stuff before 3.0 release, I guess now is the best time to rebase? <3 |
There are a few changes that need to be made for 2.99.18 (adjust a patch file, disable an image format that's not packaged) I have 2.99.18 tested and running here https://git.sr.ht/~fd/nix-configs/tree/main/item/pkgs/gimp-devel/default.nix |
Using the latest commit as of 09.03 ( The little GIMP loader popup appears, runs through fully, and then when gimp is supposed to actually appear, it crashes with the following dump: Full Dump
Stack trace:
|
Trying to see if we need any changes on Darwin.
Depends on #73833