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
On Mon, Dec 28, 2009 at 9:06 PM, Rémi Cardona <remi@g.o> wrote:
>
> RESOLVED -> WONTFIX
>
> Others and myself have spent considerable time making those deps the way
> they are because :
>
> 1) upstream packaging is a bit uncommon
> 2) ebuild deps don't fit with upstream deps
> 3) a few embedded devs told me they wiped /usr/include when making images
What all this has to do with the fact that they are just build dependencies? Just wondering.
>
> So if you want to fix this properly, a new DEP variable needs to be
> cooked up : "add the following deps to ebuilds' DEPEND when those ebuids
> DEPEND on this ebuild".
Other package managers out there have explicit build dependency lists, so, if DEPEND is not really a list of build dependencies, yeah, I agree, we need a list describing "strict" build dependencies.
>
> Until such a variable exist, having the protos in both DEPEND and
> RDEPEND is the only _valid_ solution.
>
> Thanks
Others here gave opposite opinion by the way.
>
> Rémi
>
>
--
Fabio Erculiani
http://www.sabayon.org
http://www.gentoo.org
|
|
