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] Is portage (/usr)/bin-merge safe?
Date: Sat, 1 Jun 2013 05:36:28 +0000 (UTC)	[thread overview]
Message-ID: <pan$7796a$b69709b7$19290aaf$1cb9a749@cox.net> (raw)

As in subject, is portage bin/usr-bin merge safe?

It appears most of my clashing files are /usr/bin/* -> /bin/* symlinks.  
(That's just bin, I've not looked at sbin.)

Does portage "just do the right thing" if the dirs are linked to each 
other?

Meanwhile, a quick eyeball of the results says 50-60% of the hits are 
coreutils, so if portage doesn't handle it automatically, fixing it for 
just that one package, even just using a USE flag instead of trying to 
detect it automatically, would kill a majority of the birds with a single 
stone.

(Since I don't have a separate /usr anyway, I've been thinking about 
it...  If it's not easily doable anyway, that cuts short the internal 
debate.)

-- 
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:[~2013-06-01  5:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01  5:36 Duncan [this message]
2013-06-01  5:49 ` [gentoo-portage-dev] Is portage (/usr)/bin-merge safe? Zac Medico
2017-12-07  8:37   ` [gentoo-portage-dev] " Duncan
2017-12-07  9:07     ` Zac Medico
2017-12-07 12:14       ` Duncan
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$7796a$b69709b7$19290aaf$1cb9a749@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