From: Rumen Yotov <rumen_yotov@dir.bg>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] How well supported is collision-protect?
Date: Thu, 28 Apr 2005 07:52:28 +0300 [thread overview]
Message-ID: <42706C0C.7030905@dir.bg> (raw)
In-Reply-To: <1114656028.19023.19.camel@vertigo.twi-31o2.org>
Chris Gianelloni wrote:
>On Thu, 2005-04-28 at 10:14 +0900, Georgi Georgiev wrote:
>
>
>>Uh, I did not expect such a response. I personally have a whole bunch of
>>collisions on my system, most of which man pages.
>>
>>http://gg3.net/~chutz/gentoo/collisions
>>
>>I'll see to report them.
>>
>>
>
>My suggestion:
>
>Make sure that you've installed fresh from 2005.0, as there were tons of
>collisions caused by files from the older stage1 and stage2 tarballs
>that have been fixed since 2005.0, where we changed how the stage
>tarballs worked.
>
>
>
Hi,
Can confirm that (much less collisons with 2005.0), but as there exist
some persistant collisions (nvidia-kernel, alsa-driver, some perl
modules, etc.) So i've put these in package.features/package.env file
(from Portage-Toys tools) to disable "collision-protect" just for them.
Also thinking about again begin using "maketest" and do the same for
failing packages, but not sure as there were quite a bit of packages
that didn't pass the "tests".
HTH. Rumen
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-28 4:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 0:29 [gentoo-dev] How well supported is collision-protect? Georgi Georgiev
2005-04-28 0:37 ` Mike Frysinger
2005-04-28 1:14 ` Georgi Georgiev
2005-04-28 1:27 ` Mike Frysinger
2005-04-28 2:40 ` Chris Gianelloni
2005-04-28 4:52 ` Rumen Yotov [this message]
2005-04-28 4:59 ` Mike Frysinger
2005-04-28 22:51 ` [gentoo-dev] " R Hill
2005-04-28 1:41 ` [gentoo-dev] " Marius Mauch
2005-04-28 2:19 ` Alec Warner
2005-04-28 0:50 ` Hasan Khalil
2005-04-28 12:10 ` Michael Cummings
2005-04-28 12:49 ` Georgi Georgiev
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=42706C0C.7030905@dir.bg \
--to=rumen_yotov@dir.bg \
--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