From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Council meeting: Tuesday 11 November 2012, 19:00 UTC
Date: Thu, 8 Nov 2012 12:25:27 -0600 [thread overview]
Message-ID: <20121108182527.GA3931@linux1> (raw)
In-Reply-To: <CAGfcS_=5_Yzp2gt8D3y1LGkAQ=AnudAZZNO+SbubAjYZk-iUDw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2021 bytes --]
On Thu, Nov 08, 2012 at 12:46:20PM -0500, Rich Freeman wrote:
> On Thu, Nov 8, 2012 at 11:30 AM, Alexis Ballier <aballier@gentoo.org> wrote:
> > On Tue, 6 Nov 2012 22:28:16 +0100
> > Fabian Groffen <grobian@gentoo.org> wrote:
> >> - approve/disapprove removal of gen_usr_ldscript
> >
> > I'm not sure what you meant here, but if that meant 'make it a no-op on
> > systems where it makes sense', then fine by me. Otherwise, please keep
> > in mind that removing it will also affect g/fbsd where this is still
> > needed in order to have a sane / and /usr separation.
>
> I haven't really seen any discussion of this so I'll chime in.
>
> Up until now most of the discussion has been about ALLOWING
> maintainers to stick boot-required files in /usr at some point in the
> future. Changing things like gen_usr_ldscript would actually
> represent an active push towards moving these files into /usr. I
> think that is a big distinction, and it would cause our Linux vs BSD
> approaches to diverge unless we forced BSD to follow along.
There's no reason to make *bsd do anything. gen_usr_ldscript is already
smart enough to not do anything in some environments; I'm just
proposing adding linux to that list.
> I think there is a difference between allowing a few Linux-only
> packages to move to /usr to follow upstream and moving towards a full
> scale /usr migration on Linux for all packages, even if their
> upstreams don't use /usr.
I'm not talking about migrating *anything* at this point, just how to
implement separate /usr support on linux, without affecting what the
alternate platforms are doing.
> I think the more conservative approach is to take things one step at a
> time - after some period of time allow things to move to /usr, but
> leave it up to maintainer discretion, since they're the ones getting
> bugs from linux, BSD, etc.
Please let's keep this thread on topic. Migrating packages is another
separate discussion.
Thanks,
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-11-08 21:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 21:28 [gentoo-project] Council meeting: Tuesday 11 November 2012, 19:00 UTC Fabian Groffen
2012-11-08 16:30 ` [gentoo-project] Re: [gentoo-dev-announce] " Alexis Ballier
2012-11-08 17:46 ` Rich Freeman
2012-11-08 18:25 ` William Hubbs [this message]
2012-11-08 17:45 ` [gentoo-project] " William Hubbs
2012-11-08 18:15 ` Fabian Groffen
2012-11-08 18:53 ` William Hubbs
2012-11-08 21:16 ` Rich Freeman
2012-11-08 22:09 ` William Hubbs
2012-11-08 22:28 ` Rich Freeman
2012-11-08 23:46 ` Alexis Ballier
2012-11-09 5:13 ` William Hubbs
2012-11-09 11:19 ` Rich Freeman
2012-11-09 11:33 ` Alexis Ballier
2012-11-09 15:32 ` William Hubbs
2012-11-09 16:03 ` Rich Freeman
2012-11-09 17:01 ` William Hubbs
2012-11-09 18:21 ` Fabian Groffen
2012-11-10 1:42 ` William Hubbs
2012-11-10 9:00 ` Fabian Groffen
2012-11-10 19:37 ` William Hubbs
2012-11-10 19:39 ` Ian Stakenvicius
2012-11-10 21:10 ` [gentoo-project] Council meeting: Tuesday 13 " Petteri Räty
2012-11-11 8:51 ` Fabian Groffen
2012-11-11 18:43 ` William Hubbs
2012-11-09 18:21 ` [gentoo-project] Council meeting: Tuesday 11 " Alexis Ballier
2012-11-09 8:26 ` Fabian Groffen
2012-11-11 8:53 ` [gentoo-project] [corrected date] Council meeting: Tuesday 13 " Fabian Groffen
2012-11-11 10:57 ` [gentoo-project] Council meeting: Tuesday 11 " Ulrich Mueller
2012-11-17 19:02 ` [gentoo-project] Summary Council meeting Tuesday 13 November 2012 Fabian Groffen
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=20121108182527.GA3931@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-project@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