| Re: [proaudio] (cvs|svn|git) vs 9999 |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] (cvs|svn|git) vs 9999
- From: Dominique Michel <dominique.michel@xxxxxxxxxxxx>
- Date: Fri, 11 Aug 2006 12:10:51 +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, 11 Aug 2006 10:06:37 +0200,
Frieder Bürzele <evermind@xxxxxxxxxxxxx> a écrit :
> carmen wrote:
> > wondering if theres any concensus on -9999 versions vs seperate -cvs directories? with 9999, with -cvs, it breaks the continuity of one directory per package, and additional checks must be added to avoid conflicts.
> >
> > as an example, ive installed libgig-cvs. now on a -DNuav world, its trying to install libgig-2.0.2. i had to add libgig-9999 to package.provided (thus the seperate -cvs version didnt prevent me from /etc/portage file editing after all. id rather edit package.keywords once to enable -9999 version than have to continually do -uav to make sure non-cvs versions arent being brought in beacise i didnt populate package.provided.. preemptive handling of the situation.
> >
> > another example is the patchage-cvs and om-cvs ebuilds that i submitted a while ago. the author has changed to SVN, at a different host. at this point, the -cvs should be changed to -svn to be consistent (but still no consistency to whether a 'unreleased' version is -cvs, -svn, -git, -bzr, -mercurial, or what... confusing users as to which version to try). also it doesnt show up in eg eix or esearch 'available versions'.
> >
> > in any case, my vote is for -9999. this is what the main portage tree does as well..
> >
> > c,c
> >
> >
> first I just wanted to have -cvs -svn, -... in the overlay to see
> clearly if it's a -cvs -svn, -... snapshot or not.
> But over time I feel like using -9999 is the better way as it minimize
> (I hope) maintenance.
>
> So If I change all -cvs -svn, -... to -9999 what keywords should they be?
> ~xARCH or -*
>
> @all
> please express your opinions? Should we change to 9999?
>
> Greetz
> Frieder
>
>
>
>
I don't care as long at it's work. But it is a good idea if it will
minimize the maintenance,
For the keyboard, I don't know what will append if gentoo have a ~arch
version when we have the same program also with ~arch. It portage will
choose in all cases the -9999 in the overlay, I prefer ~arch, but if it
is not the case, -* will be better. So, can we have a certitude with
~arch? I thing at the worst case will be if portage have a -9999 ~arch
ebuild at the same time as the overlay.
Cheers,
Dominique