Bug#338789: cogito packages
On Tue, Nov 15, 2005 at 01:00:48PM -0500, Andres Salomon wrote:
> On Tue, 2005-11-15 at 17:36 +0000, Gerrit Pape wrote:
> > o complete repackaging without debhelper or any other build system, I
> > usually use a simple collection of implicit Makefile rules for my
> > packages
>
> This I disagree w/; debhelper is quite valuable, and keeps a lot of the
> manual labor involved w/ package maintenance to a minimum.
Well, some years ago, debhelper tricked me sometimes, and I was forced
to spend time adapting the package just because of debhelper.
Additionally it makes backporting to previous releases more complicated,
this was with potato, woody, and now sarge. The implicit rules provide
some of the core features of debhelper, and automate the core of
packaging stuff.
Please take a look at the dash package as example, and its
debian/implicit and debian/rules, git/cogito would be even simpler with
a make install DESTDIR='$(DIR)'.
> > o try to solve the git<->git conflict with gnu interactive tools, for
> > now keep the name 'gt' for the git wrapper
>
> I was thinking of just doing a conflicts w/ git; it would violate
> policy, but it should only be temporary. I wouldn't want to see
> git-core with 'gt' enter etch, have people get used to it, and then have
> to wait for git-core with 'git' to get into etch. Better to just keep
> the same name, and leave it out of etch for the time being (imo).
Yes I agree. Moving the current git package from optional to extra and
a conflict would be a good solution IMO.
Regards, Gerrit.
Reply to: