Re: [proaudio] Importing ladi overlay to proaudio overlay

[Dominique Michel <dominique.michel@xxxxxxxxx>]

Le Fri, 28 Dec 2012 01:13:36 +0100,
Dominique Michel <dominique.michel@xxxxxxxxx> a écrit :

> Le Wed, 26 Dec 2012 00:38:04 +0100,
> Karl Lindén <spray.sucks@xxxxxxxxx> a écrit :
> 
> > Thanks for your answers so far! We will wait a little while until we
> > start the import just so everyone can have their say (in case
> > someone is on vacation due to Christmas).
> 
> Another issue I can see is the dependencies on lash. Some (many?) of
> them are in portage, that is outside the overlay control. Another
> issue is that many of them are in the overlay and it will be time
> consuming to fix them all. Because of that, a world update with both
> overlays is a nightmare at that time. So we must use a way that
> satisfy both portage and the overlay.
> 
> A solution I can see is to move media-sound/lash to
> media-libs/liblash (this is a lib, it isn't?) and media-sound/ladish
> to media-libs/ladish.
> 
> We need a new media-sound/lash package with a ladish USE and something
> like:
> 
> if use ladish ; then
> 		RDEPEND="media-libs/liblash"
> else
> 		RDEPEND="media-libs/ladish"
> fi
> 

It doesn't work, but the following work:

RDEPEND="ladish? ( media-libs/ladish 
		!media-libs/lash )
	!ladish? ( media-libs/lash 
		!media-libs/ladish )"

I will check later

RDEPEND="ladish? ( media-libs/ladish )
	!ladish? ( media-libs/lash )"

> virtual/liblash must be changed to depend on
>     || ( media-libs/liblash media-libs/ladish )
> 
> That way, ebuilds using both media-sound/lash and virtual/liblash will
> be happy with the lash depend, and we will not be stressed, or forced
> to add packages from the main tree.
> 
> Ciao,
> Dominique
> 
> 
> 


-- 
"We have the heroes we deserve."