From: Jonas Stein <jstein@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Marek Szuba <Marecki@gentoo.org>
Subject: [gentoo-dev] Re: Last rites: media-gfx/gmic
Date: Thu, 26 Oct 2023 03:29:26 +0200 [thread overview]
Message-ID: <254730d8-2987-49b8-9ca7-2e50a071b121@gentoo.org> (raw)
In-Reply-To: <eee63c4a-c05f-41eb-bff5-81036d84d561@gentoo.org>
Hi Marecki,
this is a very powerful package with many users.
Thank you for maintaining it till now.
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.
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.
I suggest to keep it for a few more months.
On 2023-10-26 03:00, Marek Szuba wrote:
> Upstream uses a massive home-made Makefile which has since the beginning
> required massive amounts of patching to make it behave reasonably
> (as well as to fix the problems which ostensibly led upstream to
> abandoning CMake, and which they immediately re-introduced in their NIH
> solution) and which if anything have only got worse since then. One,
> optional, reverse dependency in the tree.
> Removal on 2023-11-26. Bug #916289.
--
Best,
Jonas
next prev parent reply other threads:[~2023-10-26 1:29 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 ` Jonas Stein [this message]
2023-10-26 3:41 ` [gentoo-dev] " 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
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=254730d8-2987-49b8-9ca7-2e50a071b121@gentoo.org \
--to=jstein@gentoo.org \
--cc=Marecki@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