public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Making a common sub-profile for no-multilib
Date: Thu, 3 Jul 2014 11:43:48 +0200	[thread overview]
Message-ID: <20140703114348.7aaa9ddc@pomiot.lan> (raw)
In-Reply-To: <pan$94f75$9ed7a215$a2f7c848$6221cba3@cox.net>

[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]

Dnia 2014-07-03, o godz. 09:05:47
Duncan <1i5t5.duncan@cox.net> napisał(a):

> 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! =;^)

Symlinking anything to lib wasn't ever a particularly good idea. We
will spend a lot of effort fixing that (see the SYMLINK_LIB=no bug [1]).

[1]:https://bugs.gentoo.org/show_bug.cgi?id=506276

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

  reply	other threads:[~2014-07-03  9:44 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
2014-07-03  9:43                   ` Michał Górny [this message]
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=20140703114348.7aaa9ddc@pomiot.lan \
    --to=mgorny@gentoo.org \
    --cc=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