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: Dominique Michel <dominique.michel@xxxxxxxxx>
- Date: Fri, 28 Dec 2012 17:44:35 +0100
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEXy8ubtkoXo7+b1+fbN cGKCeWDtamweFA8eMkmKPkPtvcWRoqyV0Pn7AAACbElEQVQ4jXXTMWvbQBQA4MOlizsdXEXp KAi09mKcLZ0EJxONDRJVkikg9AtqTm63gtHDmVJs1GsnC0JiaTMJGN2f67uzznJb+gZj9PFO 7717IqdtvCAmem4bxMLp/2BEyEBF1+U/0H8uhI6rv+BVLNrY/gH9T0L8yAxk2yMY3YuZxDCn TY/gpBByyTGktIcZOIvFjPNJmqYJDwrx3cIoBrE0zzG4FF8tfBAwM+DonKCYWjgROZ6Upjcm 5Qje58JAmlKKGfIAjzaDUuogZBY2Bjg14eDbywMIqZvwqgqFBcVFB0seYONLb00ZZlh4p0F6 FHNoUMyKAzxowJSQTyj+XloYs3MN3GeMpzyYSTMshLM00ODpWlPp4SDbqs4cViDcGAgmlK/a PsaOg7DvIQ3wzANMqB/iQW/XTkoTLO6XhSeHUoQKe+NLjyY/Ldx7CW2D4WTYhZ3V0GP64RpP Q/E66IUWMLj3+nDn4w2ejMACyXFeHZy6ETcZehc49bv1GQ/0bazNuzm97mDkhnoie9i30WYM w/YCnYT7Fx308s98n0IT//Jod1+aOzdzYXLVbftol+PC+REG3u+0AxdEtuSMB6G+DLGwMH4E vXGmJn8VCLM9LhmrOAMQYt5Wi/DFgIC52iFkUzMpDVmjAaDZRGC+JGwDqzJ/G5fUUcWZAaE7 YfvPLYtIU1Wb4A2IeS7uDMgcIFutiCr766qGfKHyuxvTIERKXVNSN27lDgCuBuojlpxIyJV6 ritS1uWWuHF2Ww7qcIKbqEFVNbmtmm3vGSCHbVXjikrY3SpVxwQWw2aIjwG+ueXTJDmHeK6a HfwGyU5ZSlGeSRQAAAAASUVORK5CYII=
Le Fri, 28 Dec 2012 11:24:07 +0100,
Karl Lindén <spray.sucks@xxxxxxxxx> a écrit :
> 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 need media-sound/lash to satisfy portage dependencies. If you read
again my preceding mail, media-sound/lash is some kind of virtual
package that depends on either media-whatever/lash-whatever or
media-whatever/ladish. With the ladish USE flag, any user can easily
choose between lash and ladish.
>
> 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.
This is also what I think, and what I have done in my system.
virtual/liblash must install the "virtual" lash ebuild, so it will be
no blocking between virtual/liblash and media-sound/lash -- Remember,
media-sound/lash and media-sound/ladish are mutually exclusive. If
virtual/liblash install ladish directly, and some portage ebuild
want media-sound/lash, portage will issue a blocking because of the
blocking into virtual/liblash. This is also why the USE flag into
media-sound/lash is needed and simple to implement.
If portage adopt virtual/liblash, it would be possible to change it and
make it to depend on lash or ladish directly. It would also be possible
to remove the ladish USE from media-sound/lash.
Dominique
>
> 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."
> >>
> >>
>
>
--
"We have the heroes we deserve."