From: "Joshua Murphy" <poisonbl@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] First Portage Hick-up, Chokes on Java
Date: Thu, 6 Nov 2008 10:24:17 -0500 [thread overview]
Message-ID: <c30988c30811060724y561a35ffqd67b27b4ffee8d51@mail.gmail.com> (raw)
In-Reply-To: <20081105151652.GA5170@princeton.edu>
On Wed, Nov 5, 2008 at 10:16 AM, Willie Wong <wwong@princeton.edu> wrote:
> On Tue, Nov 04, 2008 at 05:23:58PM +0200, Penguin Lover Alan McKinnon squawked:
>> On Tuesday 04 November 2008 16:16:30 Jorge Peixoto de Morais Neto wrote:
>> > collision-protect seems nice, but I don't know about its drawbacks (if
>> > any), and since it seems not to be default and I don't have good
>> > knowledge of it, I didn't change the default.
>>
>> You probably want this enabled. I think it's disabled by default because new
>> users will have no idea whatsoever what to do about it. All it does is check
>> the files it wants to install with what's on the disk. If there's a match,
>> the existing files must only have been put there by the same package
>> (ignoring version numbers).
>>
>> If there's a collision, you get a huge big fat error message and a chance to
>> find out why two different packages install the same file. Maybe you need to
>> uninstall one, maybe it doesn't matter. If it's the latter, just
>>
>> FEATURES="-collision-protect" emerge <package>
>>
>> and continue as normal. In any event, you get to decide what should happen.
>> Every experienced gentoo user should be using this imho
>>
>
> On my version of portage (2.2_rc13; but I am pretty sure this is the
> case for some older ones too), there is the default feature
> "protect-owned" which provides more or less the same function as
> collision-protect but is slightly smarter. See 'man make.conf' for
> details.
>
> W
> --
> Don't tell anyone, but duct tape is The Force. It has a dark
> side, and a light side, and it binds the Universe together.
> Sortir en Pantoufles: up 698 days, 13:54
Commit to the source tree for portage:
"Add support for FEATURES="protect-owned" which is identical to the [...]"
zmedico - August 30, 2008
First portage release after that commit (according to the changelog
for sys-apps/portage, no mention of the feature's presence popping up
anywhere in the changelog, though).
portage-2.2_rc9 - 21 Sep 2008
--
Poison [BLX]
Joshua M. Murphy
prev parent reply other threads:[~2008-11-06 15:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 2:08 [gentoo-user] First Portage Hick-up, Chokes on Java boslists
2008-10-03 2:30 ` Dale
2008-10-03 2:54 ` boslists
2008-10-03 2:49 ` [gentoo-user] " »Q«
2008-10-03 2:58 ` boslists
2008-10-04 11:22 ` b.n.
2008-10-04 11:54 ` boslists
2008-10-04 16:48 ` Dale
2008-10-03 2:53 ` [gentoo-user] " Volker Armin Hemmann
2008-11-04 14:16 ` Jorge Peixoto de Morais Neto
2008-11-04 15:23 ` Alan McKinnon
2008-11-04 17:56 ` Jorge Peixoto de Morais Neto
2008-11-04 18:26 ` Alan McKinnon
2008-11-04 18:47 ` Jorge Peixoto de Morais Neto
2008-11-05 15:16 ` Willie Wong
2008-11-05 15:27 ` Jorge Peixoto de Morais Neto
2008-11-06 15:24 ` Joshua Murphy [this message]
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=c30988c30811060724y561a35ffqd67b27b4ffee8d51@mail.gmail.com \
--to=poisonbl@gmail.com \
--cc=gentoo-user@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