Can I use Macports for Gimp maintenance?

[Lukas Oberhuber]

Sorry, failed to include mailing list...

>> We use Circle CI which doesn’t go that far back either (only 4
versions). If any of you are interested in how we do it today, here’s the
repo:
>> https://gitlab.gnome.org/Infrastructure/gimp-macos-build

> Lukas, it would be great if you’re able to use MacPorts to package GIMP,
and we’ll certainly do whatever we can to support your efforts!

Really appreciated. A team that is excited and willing to help is a big
deal.

I have paused for now on Macports because:

   - too many complications including not all the packages installing
   - frequently not respecting the -x11 +no_x11 +quartz -python27 variants.
   - This meant that macports still using X11 couldn't be worked around.
   - Not clear how I do custom ports given problems above (and then if
   there are too many to make it worth it).


Positives:

   - Was able to get builds for older SDKs

Here is an MR with the work in progress for Macports:
https://gitlab.gnome.org/Infrastructure/gimp-macos-build/-/merge_requests/121

I've now shifted to trying similar on homebrew. I've been able to patch to
get earlier SDKs, and have the application running, but with a few problem
packages.

Things I still need (or need to try):

- Ability to (by default) create debug builds (helps for crash reports)
(may just be more env variable trickery)
- Test that package building indeed works properly (the ultimate goal)
- Make sure that I've reduced my maintenance burden (on homebrew this is
maintaining my own Tap, not sure on MacPorts).

For reference, I'm packaging the latest of most packages for both Gimp 2.10
and 2.99, and then for gimp 2.99 also HEAD Gtk3 and patched Cairo. Babl and
Gegl typically are revved at the same time as a new version of Gimp.

On Wed, 6 Jul 2022 at 21:31, Christopher Nielsen <mascguy at rochester.rr.com>
wrote:

> > We use Circle CI which doesn’t go that far back either (only 4
> versions). If any of you are interested in how we do it today, here’s the
> repo:
> > https://gitlab.gnome.org/Infrastructure/gimp-macos-build
>
> Lukas, it would be great if you’re able to use MacPorts to package GIMP,
> and we’ll certainly do whatever we can to support your efforts!
>
> I’ll start with a quick summary of where things stand, in case you haven’t
> done a lot of in-depth digging yet:
>
> * glib2: We currently maintain three versions:
>         * The default is 2.64.6, via port ‘glib2'
>         * The next rev up is 2.66.8, via port 'glib2-devel'
>         * And finally, the newest stable release is 2.72.3, via port
> 'glib2-upstream’
>         * If you have a preference, you’ll want to install the desired one
> first. All dependents are setup to work with all three though, and will
> automatically use whichever one you have installed.
>
> * Presently we only apply a small subset of patches for GIMP and gtk-2.
> (Though we’ve tried to cover the heavy-hitters, particularly related to
> screen-update performance on the latest macOS releases.) So if there are
> any that fix/improve runtime behavior, let me know!
>
> Cheers,
> -Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20220708/4d73d8bd/attachment.htm>