public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: R Hill <deemkay@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: How well supported is collision-protect?
Date: Thu, 28 Apr 2005 16:51:18 -0600	[thread overview]
Message-ID: <d4rp2k$7q5$1@sea.gmane.org> (raw)
In-Reply-To: <42706C0C.7030905@dir.bg>

Rumen Yotov wrote:
> 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".

If you do decide to start using the test feature, i've been using bug 
#73031 is a tracker for system packages (that is, packages included in 
'emerge system', not packages in category sys-...).  For world packages, 
you might get a thanks or you might get cussed at and your bug closed as 
invalid, depending on the maintainer.  Best to include patches.  ;P

-- 
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-04-28 22:51 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
2005-04-28  4:59         ` Mike Frysinger
2005-04-28 22:51         ` R Hill [this message]
2005-04-28  1:41   ` 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='d4rp2k$7q5$1@sea.gmane.org' \
    --to=deemkay@gmail.com \
    --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