On Fri, Sep 21, 2007 at 04:53:34PM +0930, Ron <[EMAIL PROTECTED]> wrote: > On Fri, Sep 21, 2007 at 07:42:52AM +0200, Mike Hommey wrote: > > On Fri, Sep 21, 2007 at 10:49:26AM +0930, Ron <[EMAIL PROTECTED]> wrote: > > > Package: wnpp > > > > > > * Package name : gitpkg > > > Description : helper scripts for maintaining packages with git > > > > > > This packages provides some simple scripts that assist with maintaining > > > Debian packages in git. > > > . > > > gitpkg - creates a source package from tagged revisons. > > > git-debimport - creates a git repository from a set of existing packages. > > > > Couldn't that be merged with git-buildpackage ? > > Well, they are kind of orthogonal, so I don't really see what sense that > would make. If you are using the git-buildpackage framework, then you > don't really need these scripts (...)
Actually, I don't see why it's necessary to have a package for 2 scripts that might not be even 100 lines each. These scripts could be distributed with git-buildpackage. There is no reason git-buildpackage should be limited to the set of scripts it already contains, or a single possible workflow for using git to maintain debian packages ? What are we going to see next ? Yet another package because someone else will feel none of gitpkg or git-buildpackage fit his needs ? Why not have only one package containing different tools that fit different needs ? Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
