| Re: [proaudio] Various issues |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] Various issues
- From: Dominique Michel <dominique.michel@xxxxxxxxx>
- Date: Fri, 1 May 2009 18:59:36 +0200
- 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, 1 May 2009 18:46:28 +0200,
Arve Barsnes <arve.barsnes@xxxxxxxxx> a écrit :
> > Hope this helps and best regards,
> > Gavin
>
> Strange that, I had the 0.3.1 ebuild in my pro-audio tree, but I guess
> I made it myself, thinking that a sync would delete it. Deleting that
> file manually naturally made the error disappear, and portage does not
> want to downgrade me anymore. Thanks for the tip!
>
> Regards,
> Arve
>
>
Portage is very sensitive with the overlay because the audio pro overlay know
only what is into the overlay svn repository. If you want to make any change
into the overlay, it is much better to make a personal and separated overlay for
that. To incorporate it into portage, you can add it
into /usr/portage/local/layman/make.conf after $PORTDIR_OVERLAY.
As example:
PORTDIR_OVERLAY="
/usr/portage/local/layman/pro-audio
$PORTDIR_OVERLAY
/usr/portage/local/test"
Make the changes into the test overlay. That way, if you have 2 ebuilds with the
same name and version and one of them into the test overlay, portage will
install the program using the ebuild into the test overlay.
Cheers,
Dominique