public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Last rites: media-gfx/gmic
Date: Tue, 31 Oct 2023 07:05:24 +0000	[thread overview]
Message-ID: <877cn3z2ys.fsf@gentoo.org> (raw)
In-Reply-To: <llha7vwdrwwbrlhlddyucu6fzq7n7g2jsaqtchiynakhfhpj7n@tzokpo62kaji>


Zoltan Puskas <zoltan@sinustrom.info> writes:

> [[PGP Signed Part:Undecided]]
> On Fri, Oct 27, 2023 at 12:24:32PM +0100, Marek Szuba wrote:
>> On 2023-10-26 02:29, Jonas Stein wrote:
>> 
>> > this is a very powerful package with many users.
>> 
>> ...but sadly, very few maintainers. It was m-n when I took it over 3 years
>> ago, as apparently no-one found it worth looking after following the
>> disbanding of the Graphics project - and that was back when upstream still
>> used CMake! Telling the truth I wasn't exactly interested either, it's just
>> that it happened to be an optional dependency of media-gfx/darktable.
>> 
>> > Thank you for maintaining it till now.
>> 
>> You're very welcome!
>> 
>> > Could you address the exact problems to upstream, so they are aware and
>> > can improve it?
>> > I think not only Gentoo, but also other distributions suffer if it does
>> > not build smooth.
>> 
>> I used to do that. It seemed to have little to no effect so in the end I
>> just gave up.
>> 
>> > Looks to me as if the package is not broken now, but there is a lack of
>> > manpower to update it. 30 days is the minimum for a removal.
>> 
>> There are two outstanding QA issues (ignored LDFLAGS and pre-stripped
>> binaries) in 3.3.1 pertaining to USE=gimp and USE=qt5. Prior to adding that
>> version I tried to leverage qmake-utils.eclass in the Qt parts of the
>> package, which hopefully would have got rid of these issues - but resulted
>> in a wall of actual errors. This has been the last straw as far as me
>> maintaining G'MIC is concerned.
>> 
>> > I suggest to keep it for a few more months.
>> 
>> Fine by me if someone actually maintains it. I've just dropped
>> media-gfx/gmic back to m-n to make it clear that I do not intend to block it
>> from being reactivated.
>> 
>> -- 
>> Marecki
>> 
>
> This is quite a loss. Ever since the dropping the gimp-resynthesizer plugin (due
> to Python2 deprecation) gmic was the last package to provide "heal selection"
> functionality in GIMP. Losing gmic will put GIMP behind other image editing
> software by a significant margin.
>
> I'm wondering if we could collaborate with other distro developers on building
> and improving the state of this package. E.g. Debian seems to be packaging gmic
> by itself and also for gimp and krita. I wonder if it's possible to build the
> gimp plugin portion only and not deal with gmic QT frontend?

https://github.com/GreycLab/gmic/issues/17 indicates upstream are open
to PRs at least.

>
> Zoltan
>
> [[End of PGP Signed Part]]



      reply	other threads:[~2023-10-31  7:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26  1:00 [gentoo-dev] Last rites: media-gfx/gmic Marek Szuba
2023-10-26  1:29 ` [gentoo-dev] " Jonas Stein
2023-10-26  3:41   ` Eli Schwartz
2023-10-27 11:52     ` Marek Szuba
2023-10-27 11:24   ` Marek Szuba
2023-10-31  6:50     ` Zoltan Puskas
2023-10-31  7:05       ` Sam James [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877cn3z2ys.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox