public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jorge Peixoto de Morais Neto" <please.no.spam.here@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] First Portage Hick-up, Chokes on Java
Date: Tue, 4 Nov 2008 17:56:41 +0000	[thread overview]
Message-ID: <38af3d670811040956s620784a8w17bbcc212b14651c@mail.gmail.com> (raw)
In-Reply-To: <200811041723.58876.alan.mckinnon@gmail.com>

On Tue, Nov 4, 2008 at 3:23 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> 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
>
Nice. I actually thought that this protection was enabled by default,
and wondered what FEATURES=collision-protect did. Once I had a program
behaving weirdly, and found out that its binary (/usr/bin/stream, if
memory serves) had been replaced by an identically-named binary of
another program. I thought it was a Portage bug, but you are telling
me that Portage allows this by default.

By the way, certain parts of Portage are very scarcely document, are
they not? For examples, the FEATURES only have quick explanations in
make.conf.example, as far as I know (and I did search for more
complete explanations).

-- 
Software is like sex: it is better when it is free - Linus Torvalds



  reply	other threads:[~2008-11-04 17:56 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 [this message]
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

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=38af3d670811040956s620784a8w17bbcc212b14651c@mail.gmail.com \
    --to=please.no.spam.here@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