From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: usrmerge script
Date: Sun, 21 Mar 2021 14:22:15 -0500 [thread overview]
Message-ID: <YFec53SSS9+KmRI6@linux1.home> (raw)
In-Reply-To: <87wnu02xr2.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
On Sun, Mar 21, 2021 at 01:00:01PM -0500, Matthias Maier wrote:
> Hi William,
>
> I have migrated my system to a merged /usr a while ago.
>
> In addition to moving everything to /usr and setting up symlinks, the
> main thing I had to do was to set up a /etc/portage/bashrc hook for
> post_src_install() that would move everything into /usr.
>
> Do we have native support in portage for this now?
From what I know, you don't need that hook. The ebuilds handle this now
by using the split-usr use flag, so if you add this to
/etc/portage/make.conf you should be ok.
USE="${USE} -split-usr"
Let me know if that isn't the case.
I'm not exactly sure what portage will do without your hook though. What
happens if you remove your hook then some ebuild tries to install
something in /bin for example? I would argue that, if /bin resolves to a
path, portage should just follow the symlink and install where the
symlink points. I base this argument on the return of `test -d` for
this situation.
```
$ ln -s /usr/bin foo
$ [ -d foo ] && echo "foo is a path"
```
Thanks,
William
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-03-21 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 17:39 [gentoo-dev] rfc: usrmerge script William Hubbs
2021-03-21 18:00 ` Matthias Maier
2021-03-21 19:08 ` Luigi Mantellini
2021-03-21 19:27 ` William Hubbs
2021-03-21 19:22 ` William Hubbs [this message]
2021-03-23 9:23 ` Michał Górny
2021-03-24 5:20 ` William Hubbs
2021-03-24 7:48 ` Michał Górny
2021-03-24 15:09 ` William Hubbs
2021-03-24 17:09 ` Rich Freeman
2021-03-24 18:37 ` William Hubbs
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=YFec53SSS9+KmRI6@linux1.home \
--to=williamh@gentoo.org \
--cc=gentoo-dev@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