public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: USE flag 'split-usr' is now global
Date: Sun, 4 Aug 2019 13:01:25 -0500	[thread overview]
Message-ID: <6985a693-3257-6359-add3-9fe75af6ec2f@gmail.com> (raw)
In-Reply-To: <20190804170741.fesbfdgfs2wh2ya6@matica.foolinux.mooo.com>

Ian Zimmerman wrote:
> On 2019-08-04 12:29, Mick wrote:
>
>> https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
>>
>> Essentially the historical reasons for having a lot of separate
>> directories/ fs/partitions/disks are becoming obsolete and many of
>> them are due to merge, changing the baselayout.  I assume the move to
>> profile 17.1 to deal with the various /lib directories was the start.
> I know about the history as it relates to Unix and Linux in general.  In
> fact I think I've read that article long ago.  But the question is
> what's up in gentoo.  I suspect another potentially painful migration is
> on the horizon; it would be good to know the speed we're moving toward
> the horizon :-)
>


It was discussed on -dev in at least a couple threads I think.  I sort
of followed it and my take is, when set to on, which I think it is by
default, everything stays as it is now.  Could that change later on,
possibly.  I suspect given the change being pretty large, if it does
there will be a news item about it . Of course, that would be discussed
in advance on -dev as well. 

One way to get a heads up on this sort of thing, subscribe to -dev and
follow the threads that interest you, about upcoming changes at least. 
That's why I subscribe to -dev myself and have done so for years.  I
ignore a lot of it but the things that I think might affect me, I tend
to read those so as to figure out how it might affect me and can even
know the path going forward or how to work around it.  Just a thought.

Dale

:-)  :-) 


  reply	other threads:[~2019-08-04 18:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04 10:23 [gentoo-user] USE flag 'split-usr' is now global Kai Peter
2019-08-04 11:29 ` Mick
2019-08-04 17:07   ` [gentoo-user] " Ian Zimmerman
2019-08-04 18:01     ` Dale [this message]
2019-08-05  8:05       ` Kai Peter
2019-08-04 18:03     ` Mick
2019-08-05  1:26       ` Grant Taylor
2019-08-05 10:49         ` Mick
2019-08-05 16:17           ` Grant Taylor
2019-08-05 23:34             ` Mick
2019-08-06  2:37               ` Grant Taylor
2019-08-06 15:54                 ` Canek Peláez Valdés
2019-08-06 16:28                   ` Rich Freeman
2019-08-06 23:39                     ` Ian Zimmerman
2019-08-07  0:14                       ` Rich Freeman
2019-08-06 23:41                     ` Grant Taylor
2019-08-07  0:31                       ` Rich Freeman
2019-08-07 10:11                         ` Mick
2019-08-08  3:56                         ` Grant Taylor
2019-08-06 22:54                   ` Grant Taylor
2019-08-06 23:05                     ` Canek Peláez Valdés
2019-08-07 10:48                 ` Neil Bothwick
2019-08-07 10:58                   ` Mick
2019-08-07 11:48                     ` Neil Bothwick
2019-08-07 13:24                       ` Mick
2019-08-08  7:43                         ` Neil Bothwick
2019-08-08  9:53                           ` Kai Peter
2019-08-06  0:06           ` Ian Zimmerman

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=6985a693-3257-6359-add3-9fe75af6ec2f@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@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