Re: debian directory included in upstream
On Tue, 2005-04-12 at 22:40 +0200, martin f krafft wrote:
> also sprach Margarita Manterola <firstname.lastname@example.org> [2005.04.12.2222 +0200]:
> > It makes sense for software developers to have their own ./debian
> > directory so that they can use debian/rules binary to compile and
> > test their software while developing it.
> Huh? Why not just use ./Makefile?
> > What does not make a lot of sense is to release the .tar.gz with
> > the ./debian directory, as Steve Halasz said, it's perfectly valid
> > to have it in CVS the important point would be to convince them
> > not to include it in the release.
> I disagree. ./debian is the domain of the Debian maintainer, not of
> the upstream. Unless you are developing software *for* *Debian*
> (native), there is no reason why you should bother with ./debian at
In my case some upstream developers were debian users who liked to be
able to build debs from CVS. This has been helpful since they can make
sure the app will work ok in debian before they release. It's not
strictly necessary, but I'm glad they're thinking of Debian and don't
want to discourage them.