Re: [proaudio] I want to contribute

I am not against git but what do evermind and dominique think?
Also I think there is no need to touch svn repo. No need to rename it. We just have to migrate to git with all the repo history and users. Ones the svn repo is migrated to git and it seems to be working, we just anounce it and adjust the links. Later we can remove the non working or obsolete ebuilds.

On Nov 9, 2015 1:19 AM, "Karl Lindén" <karl.j.linden@xxxxxxxxx> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 11/09/15 00:05, Manuel Bärenz wrote:
>
>> 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.
> That might make some proaudio users unhappy when they next try to
> pull the repo, right? Rather name the new git repo "new-proaudio"?
> Or maybe I don't quite understand what "consumer" means.
>
> Also, maybe there is a shellscript-minded person here who can write
> a script that tries to emerge every ebuild and adds all those that
> didn't throw an error?
>
Hmm, I guess you are right. Maybe new-proaudio is better, but then,
when will we rename new-proaudio to proaudio? I mean at some point it
is not new anymore. For the current proaudio turns old quite quick,
and stays old.

Maybe consumer is not the correct word, but we would add the new
proaudio as a master repository to the old proaudio. That way we can
remove packages from old proaudio (just to clean it up a little bit)
but still making sure old proaudio works, just to be clean I mean.
Anyway, people using proaudio would have to add the new repository at
some point.

If no one else comes up with a script, I guess I can do it. Maybe next
weekend, since this weekend was filled with writing python scripts for
a project for school, but I am happy if someone else wants to write a
script.

Lastly, I do not feel strongly about these points. So any solution
works for me.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1

iQJ8BAEBCgBmBQJWP9iLXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQjJDQkQ0QjAzQ0JGMUVBQkJFQzM0QkQ3
NjRDMDk3OTVDODEyQjk3AAoJEHZMCXlcgSuXM7kP/1FRAqJ0cIqVgkhczy3Z/XuO
8EDtVkgvUQK24utUxt/cs/aR2yAnag7Gu+xlx0P2Ex20o5WSezyXZ8da9JJ1eQTQ
D6WQ10CEW3wG1/LJJ/p5kzgoD9JM0Hn27c2JpwmmWtqr3CKIsNilgbRDQQk+r/Pg
nNohynhvBLkgcsLZBzKS9pY0KXyyWPNiwfuzaED1RHHfny6QyxGhiwX5M7uZ/4MU
ICvGe9qBCHqCXASU39ZZSLN4onNBi0Lp8q9A8/Q4a2q54KbSWv4Wrki63mn5Okou
rafGHCbJY8QDT2Mz+itJbGZscm4KcUFKI64dRhkAdS1/ANWWiSy26wI/pGMXuGQz
jZr9Ev0LA9T7nc76Wx+AyIhuUMau3MGyQ8J9cqibb1OPj7N6OsuQfxOg4qbGXfnW
X5fpC4km1qA4cDoF6m7OtEGLjIiyAlvkk31vFoTi6FkGxvOhHCYezqjAmIfOcawI
QntO9uaLzonJsGC5WfGbdBSZs4B2DhN/crdSVS/DYqJzxqZm6sDC7aJ8R3Kg8IZC
RRVfXbocn5BxQnpIdx2CFgZsyqEtB3YcdzNGx8+Mwe6juyoZCAMjlqpQ8rT/QFUU
u+r/s9pAaOFPeX7NYWKiwjVmcdRDQdX4WgMbaCArH5jJ+ZIVYvlw39xz/AmakB6G
+VlbFQtfVwlmO6sPpoDt
=7g9O
-----END PGP SIGNATURE-----