From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
Joseph Myers <joseph@codesourcery.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: What to do about libidn?
Date: Fri, 11 Nov 2016 19:53:00 -0000 [thread overview]
Message-ID: <5f72142d-92ed-8039-fb8c-dd2981a3127f@redhat.com> (raw)
In-Reply-To: <9b77b43c-f255-6401-5648-0b5cc405cf4b@redhat.com>
On 11/09/2016 07:02 AM, Florian Weimer wrote:
> In the broader picture, I think we should discourage out-of-tree
> ports and functionality as much as possible because if something is
> not part of regular builds because it's not in the official source
> tree, we might only learn about fundamental incompatibilities after a
> release or two, which would be annoying. So I'd suggest the remove
> the add-on mechanism eventually.
Agreed.
I would also vote for out-of-tree functionality to be removed.
Users can simply have cloned trees with their own patches, and help
in the overall library maintenance or work with upstream to integrate
their changes.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2016-11-11 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 11:52 Florian Weimer
2016-11-08 15:27 ` Zack Weinberg
2016-11-08 15:59 ` Florian Weimer
2016-11-09 7:53 ` Petr Spacek
2016-11-08 23:30 ` Joseph Myers
2016-11-09 12:02 ` Florian Weimer
2016-11-09 16:03 ` Joseph Myers
2016-11-11 19:53 ` Carlos O'Donell [this message]
2016-11-10 15:32 ` Florian Weimer
2016-11-11 19:49 ` Carlos O'Donell
2016-11-11 21:16 ` Joseph Myers
2016-11-11 19:41 ` Mike Frysinger
2016-11-11 20:00 ` Carlos O'Donell
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=5f72142d-92ed-8039-fb8c-dd2981a3127f@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--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).