Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-dev@g.o
From: Richard Freeman <rich0@g.o>
Subject: Re: Closing bugs
Date: Sat, 11 Sep 2010 15:22:45 -0400
On 09/11/2010 03:04 PM, Ciaran McCreesh wrote:
> Or does the problem only occur if you mix keywords and ignore
> dependencies?

I think that if a package doesn't work in a mixed environment, that 
points to a likely dependency problem.  Sooner or later there is a good 
chance it will bite somebody.

Personally, I try to keep package dependencies correct.  If a package in 
unstable needs a library version in unstable, I depend on that version - 
not on the library itself.  Then we won't get burned in six months when 
I forget all about this or am not around and things start going stable 
in the wrong order.

Sure, if the issue is something really exotic maybe we should just say 
"don't do that," but usually there is a better fix.

Personally I welcome these kinds of bugs, as they're the easiest way to 
uncover non-obvious dependency issues that might otherwise make their 
way into stable.  Maybe we can't fix them all, but we ought not to just 
dismiss them out of hand.  I certainly wouldn't want to see the 
bug-wranglers screening for them, for instance.


Re: Closing bugs
-- Alistair Bush
Closing bugs
-- justin
Re: Closing bugs
-- Ciaran McCreesh
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Closing bugs
Next by thread:
Re: Closing bugs
Previous by date:
Re: [gentoo-commits] gentoo-x86 commit in dev-python/vo: ChangeLog vo-0.6.ebuild
Next by date:
Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyQt4: PyQt4-4.7.6.ebuild ChangeLog

Updated Jun 23, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.