[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Shishi/GSS no-symbols-control-file lintian warning

From: Simon Josefsson
Subject: Re: Shishi/GSS no-symbols-control-file lintian warning
Date: Mon, 02 Mar 2009 15:43:53 +0100
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.90 (gnu/linux)

Russ Allbery <address@hidden> writes:

> Simon Josefsson <address@hidden> writes:
>> Yes, but while I have read many blog posts with notes about maintaining
>> debian packages in git, I haven't see any single complete walk-through
>> of what I have to do to make that happen.
> I tried to document what I do at:
> Possibly of interest is that I maintain Debian packaging in the same Git
> repository as upstream development for my own packages, and exactly how to
> do that is discussed in the document.

Thanks for the pointer.

>> It seems there are many variants; some seems to put the entire tar
>> archives in git which I don't really understand the advantage in.  Do
>> you have some good links?
> Allowing generation of the upstream tarball from Git is excellent because
> it makes the Git repository completely stand-alone.  All you need is a
> clone of the repository.  You don't need any external data store in order
> to build packages.
> The best way to do this is via pristine-tar, which stores only the
> required extra information to regenerate the exact upstream tarball based
> on the tagged upstream branch.  This is a great tool.  The files that it
> has to store in the repository are usually only a few KB.

Ok.  The savannah admins doesn't want me to put *.tar.gz files into CVS,
so I presume they would have similar feelings about putting *.tar.gz
files into Git, though.  So using the upstream source repository for the
debian package files probably won't work out.

However, I can use my for this.  Or does allioth
support git hosting?  I'm not sure if I can use it as a DM though.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]