Re: [proaudio] Importing ladi overlay to proaudio overlay |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] Importing ladi overlay to proaudio overlay
- From: Karl Lindén <spray.sucks@xxxxxxxxx>
- Date: Fri, 28 Dec 2012 11:24:07 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=QUqShNaVKZNMbmlC6SXQODOuwys/ZH9ZqAeMFHuI8SY=; b=EHOsngo7OUrW9jHLtmY7PiYmlJMAXROPl2oH9f/YIiN8zs2VZtWfLdBoyDr8gduxMQ xLkdnYo53nrYTKarmlwhnExRZudUTed/ycWuDrVQHGKVuJ4Mg/OW8oLKLR2tyQOP6mf9 ZUdL5cV/z/+2zs9Z2hhEw8lyr6xASnrHL/ASDEkNk8ZZZgt46Gr6hgWjl3psIpIqu5/6 LdOt6NpUef2eFBZcyH7lYuDmKiZdq1D/rWAdWWFEAKqlTSE0Pe9ZPiIQBKsS8fgOTp9h c1Ki3L2HYWfAgSdn6u4nYl45r4I2YcjpEKSXhoTJcIulpJJcACJbXeocBND087CewcXH B/uA==
I think a better solution is renaming media-sound/lash to
media-sound/lash-real and create a "virtual" package media-sound/lash
that depends on either media-sound/lash-real or media-sound/ladish.
This is good because we don't need to categorise them as libraries.
We should also keep the real virtual virtual/liblash and use it in new
ebuilds because I think it is a cleaner solution. This can maybe be
adopted by portage in the future. That would be great, but I don't
think it's something that will happen in the near future.
Regards,
Karl
2012/12/28 Karl Lindén <spray.sucks@xxxxxxxxx>:
> Well, lash isn't just a library, neither is ladish, but for the
> convenience it's a solution
>
> Isn't RDEPEND=" || ( media-libs/lash media-libs/ladish )" better? Do
> we really need a use flag? They should block each other anyway.
>
> 2012/12/28 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."
>>
>>