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

[Lukasz Kies]

2012/7/9 Elan Ruusamäe <glen at pld-linux.org>:
> 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
Why we need mirror of our git in external system? And if there is a
valid reason, will it be read-only or read write? Which brings another
questions like access rights and synchronization...

> 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?
I believe such sources of "PLD only software" should be keep out of
packages to hightlight it's not a spec files or additional patches for
external maintained software.

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

> 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.
I see no reason to not move any alive PLD projects to git instead of
keeping it in numerous different repost (poldek anyone?). No need to
maintain so many repos. If some automation is highly depended on cvs
it should be fixed to use git.

-- 
Lukasz