public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Re: Is portage (/usr)/bin-merge safe?
Date: Thu, 7 Dec 2017 12:14:16 +0000 (UTC)	[thread overview]
Message-ID: <pan$ad2f7$4f8ee13b$acfd9ce$f0b79582@cox.net> (raw)
In-Reply-To: 6c2ee2b3-88df-e943-61d5-d1e846789ab1@gentoo.org

Zac Medico posted on Thu, 07 Dec 2017 01:07:21 -0800 as excerpted:

> On 12/07/2017 12:37 AM, Duncan wrote:
>> Zac Medico posted on Fri, 31 May 2013 22:49:02 -0700 as excerpted:
>> 
>>> On 05/31/2013 10:36 PM, Duncan wrote:
>>>> As in subject, is portage bin/usr-bin merge safe?
>>>>
>>>> It appears most of my clashing files are /usr/bin/* -> /bin/*
>>>> symlinks.
>>>
>>> I haven't tried it, but it should work just fine. Portage has always
>>> supported directory symlinks like these. I haven't heard any recent
>>> complaints regarding them.
>> 
>> As the attribution says, I'm resurrecting a thread from 2013...
>> 
>> I set up a merged /usr/bin -> /bin (and sbin -> bin, and /usr -> .)
>> soon after that, with very few problems, usually ebuilds doing
>> unconditional rms in postinst or the like, until recently...
>> 
>> Something recently changed, as now I'm having many more problems, so
>> far with four packages, glibc (!!), coreutils (!!), nano, and shadow,
>> installing symlinks that ultimately point to themselves.
>> 
> I think the sort order of your root directory changed for some reason.
> The order that readdir returns filenames depends on the filesystem
> implementation:
> 
> http://man7.org/linux/man-pages/man3/readdir.3.html

That's... strange.  Back in 2013 might have still been on reiserfs, but 
I've been on btrfs for awhile now.  I wonder what might make it change 
order?

Tho I /did/ somewhat recently upgrade ssds, thus copying the /bin dir 
and /usr -> . symlink, among other root entries.  Obviously back when I 
first setup the /usr -> . symlink it was the newest entry.  Maybe if I 
delete and recreate it so it's definitely the newest entry again...

I have no idea how long it might have been before I came up with the idea 
to try that on my own.  Thanks!  I'll (gingerly, I don't like major 
system breakage!) see if it makes a difference.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



  reply	other threads:[~2017-12-07 12:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01  5:36 [gentoo-portage-dev] Is portage (/usr)/bin-merge safe? Duncan
2013-06-01  5:49 ` Zac Medico
2017-12-07  8:37   ` [gentoo-portage-dev] " Duncan
2017-12-07  9:07     ` Zac Medico
2017-12-07 12:14       ` Duncan [this message]
2013-06-01  6:17 ` [gentoo-portage-dev] " Mike Frysinger
2013-06-02 11:14 ` vivo75
2013-06-02 11:54   ` [gentoo-portage-dev] " Duncan
2013-06-02 12:47     ` vivo75
2013-06-02 13:19       ` Duncan

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='pan$ad2f7$4f8ee13b$acfd9ce$f0b79582@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-portage-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