-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 11/08/15 23:11, Ingolf Wagner wrote: > Ok, I set up everything now. I use git svn, here is what I did. > > git svn clone > svn+ssh://[email protected]/svnroot/proaudio/proaudio > <http://[email protected]/svnroot/proaudio/proaudio> > --stdlayout --revision=2960 cd proaudio/ git svn rebase > > > I found some readme files (and a folder which I think is dead > proaudio-dev, whats that for?) I haven't read all the readme files > so far, but I looks like you have the same files on the wiki page. > > > anyway, is there any revision process in place? like pull-requests > or something? Otherwise I would just put my ebuilds in there. > > Cheers Ingolf Wagner > > p.s.: happy to be on board, and will read the readme files > tomorrow. > > > > 2015-11-05 1:28 GMT+01:00 Wayne DePrince Jr. <[email protected] > <mailto:[email protected]>>: > > Il giorno mer, 04/11/2015 alle 15.21 +0100, Manuel Bärenz ha > scritto: >> I certainly agree that moving to Git is a very good idea. I >> haven't contributed much to this overlay, and one of the reasons >> is that I couldn't be bothered to learn SVN, and didn't want to >> send patches via Email all the time. >> >> Gitlab vs. Github: I have the feeling that the issue tracker on >> Gitlab is more usable and serious than the Github one. Other than >> that I agree with Karl about the philosophy and would prefer >> Gitlab. But I wouldn't mind Github either if people think that >> popularity is important (and in case nobody wants to use Gitlab >> just because of Proaudio). >> > > +1 for GitLab: open license + better issue tracker > > thanks for moving to Git. > > > > Well, unfortunately I have not had time to do any proaudio work. I will do as soon as I get the time. Since the overlay is terribly outdated here and there and some ebuilds do no nothing but making repoman unhappy I suggest we move to git package-by-package, rather than copying everything in one go, because then we would need to janitor the overlay in order to get meaningful repoman output.
The process I suggest is the following: 1. Rename the the proaudio svn repo to old-proaudio. 2. Create a git repo at GitLab and name it proaudio. 3. Make the old-proaudio a consumer to (new) proaudio. 4. Begin moving ebuilds and make sure repoman is happy. What do you think? If no one opposes I will start doing this when I get the time. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.1 iQJ8BAEBCgBmBQJWP8rNXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQjJDQkQ0QjAzQ0JGMUVBQkJFQzM0QkQ3 NjRDMDk3OTVDODEyQjk3AAoJEHZMCXlcgSuXoYsP/AxBf/I1w7o23qlqMSR8bclc jMGzAsQ5tKQlG8DecmcOPD2hWk1dxeAmk/7TgvosinntFCBbwZszWvHOAIMn5aBT 9zuznqR4wz8vUwgNWZuNP6RWMfiL3vtUGwYa0MWzpk8XiiXKenacmonbf1elvj8j 2Ej6GwpPM0YRK62/QEo4Gcl4Hklbsir7NR3vmDvYxF9xr0T791+/YW2z0Er2sF20 IY3w+oFTDWyH5vzcVA7k/NA2nMmE58Gj+ubPiRWKW59H0FZPKXwhzNuMbtuXwGGl zHI4KaNMQaumwFqSni5iiH3IqsRjE2noSVzJZ4YUZTXv76SMDKmMzRkUa+W0OpTL h9z2gT1s154oFbbP/1+XAMDM17tWolfQWFHRu8TUuxtzo+x1OeJvP/mMVEtCnVcX rEw6fgch5aE1cKBchAxfsAYzvoo25T4FIOV1SjwzMmatvnUJSR4GdWvS2t4zYe4i IjaTQp8nPsKcLdErRK/w8kHQUKN64M7ZPmPx0k98r7OkJPhtqJ+fFsa4ZqJgmWGv MbySkLaLAh6XKi6Vl/fWXacXjwWiCxOKRMvf4BR3hS7KH7awNBMF9xTPoAFU+8pS UKBtCDvRRm4BxaijL7qiw15JICillIdMmadn+Sbf4Mk+IHgMDS2/K5cU8i09RKKY egXsqj+0lVSiczyEKS11 =ZLMl -----END PGP SIGNATURE-----
