public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] How well supported is collision-protect?
Date: Thu, 28 Apr 2005 21:49:48 +0900	[thread overview]
Message-ID: <20050428124948.GA8960@lion.gg3.net> (raw)
In-Reply-To: <200504280810.49843.mcummings@gentoo.org>

maillog: 28/04/2005-08:10:49(-0400): Michael Cummings types
> Have to pipe up on this as I get at least a half dozen bugs a week...
> 
> On Wednesday 27 April 2005 08:29 pm, Georgi Georgiev wrote:
> > On a note, similar to the one about /usr/X11R6, I'd like to ask about
> > collision-protect.
> >
> > - How well is it expected to work?
> >
> Oh, it works, believe me, it works
> 
> > - Do you guys expect bug reports about packages with conflicting
> >   targets, with possible patches, etc?
> 
> Expect is a big word. Let's just say I'm a bad dev and don't follow the list 
> of new features in every release of portage (portage folks: i love ya, you 
> know that, doesn't mean I follow all the new feature flags and all), so my 
> introduction to collision-protect was when a half dozen bugs were filed one 
> rainy morning. Perl is in a collidable situation because we offer ebuilds 
> that supercede the modules that were installed with your version of perl (on 
> account of packages needing newer modules but not newer perl's) - we get hit 
> when the man pages go to merge. I'm hoping to alleviate (NOTE: not resolve) 
> some of this when we can do versioned virtuals, but until then I sympathize 
> with the bug posters and kindly ask them to disable collision protect until 
> the module is installed.

Isn't there a way to avoid installing the modules with perl and PDEPEND
on them instead?

-- 
()   Georgi Georgiev   () It has been said that Public Relations is    ()
()    chutz@gg3.net    () the art of winning friends and getting       ()
()  +81(90)2877-8845   () people under the influence. -- Jeremy        ()
() ------------------- () Tunstall                                     ()
-- 
gentoo-dev@gentoo.org mailing list


      reply	other threads:[~2005-04-28 12:49 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         ` [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 [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=20050428124948.GA8960@lion.gg3.net \
    --to=chutz@gg3.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