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: Thu, 27 Dec 2012 19:56:45 +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 Thu, 27 Dec 2012 13:12:30 +0000,
toki clover <tokiclover@xxxxxxxxx> a écrit :
> I'd like to just add, again, that this is an occasion to migrate to
> git. Many proaudio users, including myself, will contribute with a git
> vcs instead of a subversion one. I created https://github.com/proaudio
> a few weeks ago, but nobody seems to be interested into it. I'll
> delete everything next time I have a chance to be logged as proaudio.
The 2 things are independent. Also, I use git for another project, but
for an overlay, I do prefer svn, because with svn, you can screw up
things in the layman tree (not the devel tree, the tree used by layman
and portage), and all you have to do is to delete the crewed up part of
the overlay and issue a simple "svn up". With git, you have the delete
the overlay and re-add it. After what you also have to edit the layman
configuration files if you want to change the priority between the
overlays.
Now, I know that it is not good practice to edit directly the files into
a layman managed overlay. But sometime this is just more convenient to
do so...
In fact, I don't really care as long it work. And both svn and git will
work. My main concern is time. Who want to 1) make the migration,
2) adjust the URI into the wiki, and 3) manage the commits from the
users.
1) is already done. But I would prefer to have it on tuxfamily for 2
reasons:
a) It would be straightforward to add all the devs.
b) I have very good friends and family in Cuba. I am planing to move to
this country in a few years. github is based in the US and this last
country do have a very f, hostile politics toward Cuba. I send an email
to github to know their policy toward Cuba, but I thing I already know
a part of the answer: they can make no warranty if the f. hostile US
politics toward Cuba will change for the better or the worst, and
consequently, if it will be possible to access github from Cuba in a
few years from now.
I can do 2).
If someone can answer to 3), I have no objection, I suppose I can make
1) on tuxfamily and be sure than every dev get write access to it.
Dominique
--
"We have the heroes we deserve."