public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Support for Seperate /usr
Date: Mon, 05 Aug 2013 20:32:46 -0400	[thread overview]
Message-ID: <5200442E.7010105@gentoo.org> (raw)
In-Reply-To: <CAGfcS_keiWtGjJ04yhkrSS2J682BYQBch9s1C74x9eHtB35gdQ@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/01/2013 05:16 PM, Rich Freeman wrote:
> Splitting thread so that the agenda thread isn't lost in discussion:
> 
> On Thu, Aug 1, 2013 at 4:04 PM, Alexis Ballier <aballier@gentoo.org> wrote:
>> I have no opinion whether separate usr should be supported or not: I
>> have not been using this layout since years. However, I strongly prefer
>> some kind of consistency: The traditional layout with a minimal / to
>> boot or the usr move both have their advantages; if we go for something
>> in between we get none of them.
> 
> I tend to loosely agree here.
> 
> My inclination right now is to support this proposal if either of the
> following is true:
> 1.  Somebody explains that right now the absence of a decision is
> causing them actual problems (extra work, limitations, whatever).
dozens of things have randomly been moved from /usr to / as a result
strictly of user complaints.  For instance bzip2 was moved to / but
lbzip2 is in /usr which means I can't safely do something like "eselect
bzip2" and use a properly threaded bzip2 implementation.

- -ZC
> 2.  This becomes necessary to enable some larger long-term goal, which
> has received council approval.
> 
> #2 was basically covered by Alexis already.
> 
> Regarding #1, I informally emailed the base-system maintainers a week
> ago about whether there was any need to revisit last year's decision.
> I didn't really get a sense that anybody really needed the council to
> step in now.  I recognize that William is also a base-system
> maintainer so if he wants to state that he is subject to some kind of
> extra work or such supporting separate /usr without an early boot
> workaround I'll certainly be sympathetic.
> 
> I do favor the dropping of support for separate /usr without an early
> boot workaround.  I just don't think the council should actually step
> in until somebody needs us to, or as part of some larger plan.  If the
> base-system maintainers have things under control, better to let them
> handle it.
> 
> Rich
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSAEQuAAoJEKXdFCfdEflKP5gP/jxr4FopH8XD6KPUctt7BH3/
y99DzXOFNmCFUC5AnYpkUW8XUchQv2e0Ti+OLAaTLHtvL8h2dfbQn58mDToqQGq0
Z/ifB3Pk4R31G8OzA1JL7NsQjJR3fgVALzlmD1nv7W43Jr4mMrvQtAkMbcYcDKzc
14RDkCMiewm+AAqQ6DWSuD+GM07lXw5y3aDp0vfGzgKQ2GVOXHsY77WIRFLveMrD
rWRKu8xt7WZ+t4DBl3uQm7mz0khvJnY4B1cY7SSlog8QnrXxM9ofU63RJ740MeUb
K72eWvjM/ZKbkpkjiMDKILNnuEwgCWsRXviO8DSNv1NqkQM3GkX84rMYJvtxIFSD
aYZQ9wTK7kN6gwjcH4/0zBi1xYG1krwd+sakRUsmxeMNuLgZixTa16WuB5Shfzrs
KhzfANPQAWKGchEMQlP4AJT4GyMLFhP8xe5Q6MdYesduK8GP/DQhC3xsJBzRXC7C
qUCN+5Y9Ub7Z+BWAPObW9e1fMzyiwwKLfunepkVIOYwYZsUyxfQYAMfM7VFLqtDU
x1YG9cZArPRcZJdn8LFe82o9DCyUUpaXviEePY6y+aZ+gPNWXEoBuyiiznMsXj17
T89JjJb4R74CDUniGGqKAqKqCaivm6FmUH7B11fEPe/1oEbcRUEoKDHIVxn362oy
CP8r+XZhTp5dxYplwMqh
=BGXp
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2013-08-06  0:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01 21:16 [gentoo-project] Support for Seperate /usr Rich Freeman
2013-08-01 21:42 ` Andreas K. Huettel
2013-08-01 23:26   ` Rich Freeman
2013-08-01 22:49 ` William Hubbs
2013-08-01 22:57   ` Samuli Suominen
2013-08-01 23:15   ` Rich Freeman
2013-08-02  3:04     ` Dale
2013-08-02  8:15       ` Michał Górny
2013-08-06  0:32 ` Rick "Zero_Chaos" Farina [this message]
2013-08-11 14:59 ` [gentoo-project] Support for separate /usr Ulrich Mueller

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=5200442E.7010105@gentoo.org \
    --to=zerochaos@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