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: [gentoo-dev] Last rites: net-irc/ngircd
Date: Fri, 27 Dec 2024 08:04:51 +0000	[thread overview]
Message-ID: <87plldtuu4.fsf@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

Hi,

First, I apologise for letting the package rot a bit. It's wonderful
software that's pretty neat, but I've lost all motivation for caring
for it because upstream insist on using ancient automake for its
ansi2knr tool, removed in later automake releases.

See https://github.com/ngircd/ngircd/issues/261#issuecomment-1369266180.

While we could just patch the generated configure, it's an ongoing
problem if we have to make future changes, and given I've been
championing the Modern C work, I just can't really bring myself to do it
here.

I'm last-riting net-irc/ngircd accordingly. Feel free to adopt it and
unmask it if you're willing to do that handrolling of the configure
patch for https://bugs.gentoo.org/946998 or somehow persuade upstream.

(It might be possible to maintain a tiny meson port for it. Maybe
upstream would even accept such a thing if it lived alongside autotools
in the repo.)

# Sam James <sam@gentoo.org> (2024-12-27)
# Unfixable modern C issues because of reliance on ancient automake.
# Out of date. See bug #946998. Removal on 2025-01-27.
net-irc/ngircd

thanks,
sam

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

             reply	other threads:[~2024-12-27  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27  8:04 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-27  8:09 [gentoo-dev] Last rites: net-irc/ngircd 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=87plldtuu4.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