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

Re: Bug#457353: gdome2-xslt: should not be a Debian-native package

Manoj Srivastava <srivasta@debian.org> writes:
> On Wed, 26 Dec 2007 15:23:32 +0100, Wouter Verhelst <wouter@debian.org> said: 

>> Oh, I agree. I was only talking about a situation in which the Debian
>> maintainer of a given package is the very same person as the upstream
>> developer.

>         Even in this case, I think one should consider making it
>  non-native, since in the future either the upstream task or the debian
>  developer might change; and then it will be a  nuisance to cenvert from
>  a native to a non native numbering scheme.


I also considered making several of the packages that I maintain native,
since I keep the debian directory in the upstream VCS, but decided against
it becaues of this, and also because Debian also often needs new releases
that are meaningless for people outside of Debian.  I didn't want my
non-Debian users of a package to see a version increase and a new release
when all I did was a Debian housekeeping update (update standards version,
move Homepage headers, update debconf translations, that sort of thing).

Instead, I just automated the release process, including taking a release
tarball, unpacking it, and exporting the debian directory from the VCS
before doing a build.  It makes the whole thing painless.

I keep meaning to document the script I use and put it up on the web, but
until I get around to it, it's certainly available by request.  It's
called "release", just like everyone else's script to do the same thing,
handles a few other things like PGP-signing releases and releasing
individual scripts, and is written in probably horrible Python.  (It was a
learning exercise.)

Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

Reply to: