pld-builder.new: PLD_Builder/request.py - change links from cvsweb to gitwe...

[Elan Ruusamäe]

On 07/09/2012 10:26 PM, Lukasz Kies wrote:
> git. Maybe in projects/pld/pld-builder.new?
> It's worth to move there (to pld insead to packages) also:
> - template-specs
> - buildlogs
> - pld-ftp-admin
> - cdg
> And maybe create a new repo (i.e. repo-tools) with those orphaned
> scripts from packages root dir from CVS.
in irc questions rise up, including  those and i proposed:

1. https://github.com/pld-linux - mirror of git.pld-linux.org/packages


2. https://github.com/pld-linux/rpm-build-tools is same as 
git.pld/packages/rpm-build-tools due the above

3. https://github.com/pld-linux/pld-builder.new - moved to 
git.pld/projects/pld-builder

altho it could be as well subdir of packages/pld-builder named src - 
there's no exception why not keep .spec and source code separate, is it?

4. and template-specs goes to 
git.pld/packages/rpm-build-tools/template-specs alternatively packaged 
into rpm as well.

5. and remaining scripts from packages/* go as well to 
git.pld/packages/rpm-build-tools/

all those (4-5) with cvs history import

right now i have no opinion on buildlogs and pld-ftp-admin or other 
admin/* dirs from cvs/svn, so i'd leave them where they are, they are 
not directly related to "packages development" and thus needed daily and 
for every developer. and also afaik admin/* files have some automation 
scripted somewhere.

-- 
glen