| 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: Tue, 25 Dec 2012 00:03:05 +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 Sun, 23 Dec 2012 21:32:35 +0100,
Karl Lindén <spray.sucks@xxxxxxxxx> a écrit :
> Hi!
>
> Me and Nedko Arnaudov have come up the idea of merging the ladi
> overlay to the proaudio overlay. Both overlays aim at proaudio
> production so we don't see a reason for having two overlays. This
> import would also reduce the risk of doing duplicate work and is more
> convenient as users don't need to download and keep track of two
> overlays.
>
> What do you think? Would it be a good idea? If no one opposes the idea
> we can start working immidiately.
Yes, it is a good idea. I took a fast look, and a few things need to be
fixed. First, laditools fail with
emerge: there are no ebuilds built with USE flags to satisfy
"dev-python/pygobject[introspection]".
!!! One of the following packages is required to complete your request:
- dev-python/pygobject-3.2.2-r1::gentoo (Missing IUSE: introspection)
- dev-python/pygobject-3.2.2::gentoo (Missing IUSE: introspection)
- dev-python/pygobject-2.28.6-r52::gentoo (Missing IUSE: introspection)
(dependency required by "media-sound/laditools-1.0.1" [ebuild])
(dependency required by "laditools" [argument])
Introspection support was removed from all gentoo pygobject due to
upstream recommendation # (see
https://bugzilla.gnome.org/show_bug.cgi?id=642048#c9)
I try to remove the introspection USE depend from laditools ebuild.
emerge work, but the only program that work is ladi-system-tray. All
the other programs are failing.
Another error is the URI in dev-python/enum. It begin with mirror://
This tell portage to search for the archive on the gentoo mirrors where
this file is not. Should be replaced by http://
Dominique
>
> Regards,
> Karl Lindén
>
>
--
"We have the heroes we deserve."