From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Making a common sub-profile for no-multilib
Date: Thu, 3 Jul 2014 09:05:47 +0000 (UTC) [thread overview]
Message-ID: <pan$94f75$9ed7a215$a2f7c848$6221cba3@cox.net> (raw)
In-Reply-To: 53B500CA.4080609@gentoo.org
Jonathan Callen posted on Thu, 03 Jul 2014 03:05:46 -0400 as excerpted:
> I did, however test when a package installs two (different) regular
> files into paths that end up symlinked, and found that portage does
> break in that case (as the only sensible option at that point is to
> fail, as something will be lost in either case).
Indeed, and good point.
I guess at that point it's basically a pkg-collision, except that it's in
a single package instead of two different packages. Too bad a package
can't block itself and thus handle it the way different packages blocking
each other handle that case! =;^)
That's why symlinking both lib64 and lib32 to lib isn't a particularly
good idea! =;^)
--
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
next prev parent reply other threads:[~2014-07-03 9:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 17:01 [gentoo-dev] Making a common sub-profile for no-multilib Ian Stakenvicius
2014-06-25 18:44 ` Michał Górny
2014-06-25 19:00 ` Chris Reffett
2014-06-25 19:14 ` Anthony G. Basile
2014-06-25 19:11 ` Rich Freeman
2014-06-25 20:01 ` Andreas K. Huettel
2014-07-02 13:30 ` Rich Freeman
2014-07-02 18:14 ` [gentoo-dev] " Duncan
2014-07-02 23:06 ` Jonathan Callen
2014-07-03 4:59 ` Duncan
2014-07-03 7:05 ` Jonathan Callen
2014-07-03 9:05 ` Duncan [this message]
2014-07-03 9:43 ` Michał Górny
2014-07-03 10:58 ` [gentoo-dev] " Michał Górny
2014-07-03 12:07 ` Peter Stuge
2014-07-03 12:12 ` Michał Górny
2014-07-03 12:42 ` Peter Stuge
2014-07-03 12:33 ` Rich Freeman
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$94f75$9ed7a215$a2f7c848$6221cba3@cox.net' \
--to=1i5t5.duncan@cox.net \
--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