From: Roland McGrath <roland@redhat.com>
To: Guy Martin <gmsoft@tuxicoman.be>
Cc: "Carlos O'Donell" <carlos@codesourcery.com>, libc-ports@sourceware.org
Subject: Re: Glibc-ports status? Creating glibc-ports tarball for 2.13?
Date: Fri, 18 Feb 2011 18:57:00 -0000 [thread overview]
Message-ID: <20110218185728.688301814C8@magilla.sf.frob.com> (raw)
In-Reply-To: Guy Martin's message of Friday, 18 February 2011 16:34:48 +0100 <20110218163448.75f05ecd@borg.bxl.tuxicoman.be>
I hadn't noticed this go by before, so I'm glad Joseph rejected it. I'd
like to make a stronger blanket statement. No ports add-on should ever
override a sysdeps file in the main tree. That is, it must always be a
no-op to include the ports tree as an add-on when configuring for a
non-ports architecture.
If you want to add new shared files, then the way to do that is to put them
in a new or different sysdeps subdirectory, adding Implies files as needed.
Note that doing this would break the current situation where each port can
be an independent add-on distributed separately. Up until now, they all
live in one repository/tree together only for convenience. If there is a
real need to add a new file shared across ports, we should give the issue
more careful thought before deciding how to handle it.
Thanks,
Roland
next prev parent reply other threads:[~2011-02-18 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 13:40 Carlos O'Donell
2011-02-14 13:55 ` Andreas Jaeger
2011-02-14 14:07 ` Ryan Arnold
2011-02-14 14:52 ` Matt Turner
2011-02-14 15:58 ` Carlos O'Donell
2011-02-18 15:35 ` Guy Martin
2011-02-18 18:57 ` Roland McGrath [this message]
2011-02-14 17:36 ` Andreas Schwab
2011-02-14 18:37 ` Joseph S. 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=20110218185728.688301814C8@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=carlos@codesourcery.com \
--cc=gmsoft@tuxicoman.be \
--cc=libc-ports@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).