From: Florian Weimer <fweimer@redhat.com>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>, libc-alpha@sourceware.org
Cc: Joseph Myers <joseph@codesourcery.com>
Subject: Re: Remove add-ons mechanism
Date: Thu, 05 Oct 2017 11:07:00 -0000 [thread overview]
Message-ID: <d079cb89-4f6d-31a1-623e-277383d8fe3a@redhat.com> (raw)
In-Reply-To: <3368915.savkYuAEhr@porto>
On 10/05/2017 12:39 PM, Andreas K. Huettel wrote:
> Am Donnerstag, 28. September 2017, 19:49:28 CEST schrieb Joseph Myers:
>> glibc has an add-ons mechanism to allow additional software to be
>> integrated into the glibc build.
> [...]
>> libidn used to have separate release tarballs
>> but no longer does so, but still uses the add-ons mechanism within the
>> glibc source tree.
>
> http://git.savannah.gnu.org/gitweb/?p=libidn.git;a=shortlog
>
> Doesn't look dead to me; actually the libidn inside glibc looks way outdated
> (before 2012 I think).
Joseph means glibc-libidn-2.3.4.tar.bz2 etc. available here:
<https://ftp.gnu.org/pub/gnu/glibc/>
Their packaging is completely different from the libidn upstream releases.
Thanks,
Florian
next prev parent reply other threads:[~2017-10-05 11:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 17:49 Joseph Myers
2017-09-28 22:01 ` Zack Weinberg
2017-09-28 22:38 ` Joseph Myers
2017-09-29 11:04 ` Florian Weimer
2017-09-30 6:35 ` Florian Weimer
2017-09-30 21:42 ` Joseph Myers
2017-10-05 10:39 ` Andreas K. Huettel
2017-10-05 11:07 ` Florian Weimer [this message]
2017-10-05 12:54 ` Joseph Myers
2017-10-05 13:16 ` libcidn (was: Re: Remove add-ons mechanism) Andreas K. Huettel
2017-10-05 13:39 ` libcidn Andreas Schwab
2017-10-05 13:40 ` libcidn Florian Weimer
2017-10-05 21:11 ` Remove add-ons mechanism Andreas K. Huettel
2017-10-05 21:30 ` Joseph Myers
2017-10-05 15:59 ` Joseph Myers
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=d079cb89-4f6d-31a1-623e-277383d8fe3a@redhat.com \
--to=fweimer@redhat.com \
--cc=dilfridge@gentoo.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).