martin f krafft wrote:
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
all.
What about the case in which the upstream maintainer is the Debian
maintainer? I create packages for a piece of sofware I've written (and
for which I'm looking a sponsor, see
http://lists.debian.org/debian-mentors/2005/04/msg00106.html ). The
debian/ directory is in CVS, naturally. It is currently distributed in
the .tar.gz file. Should it be removed? This would make things more
difficult for me, because in the case of a new version, I would need to
untar the new .tar.gz file and then copy the debian/ directory from CVS.
--
Are there those in the land of the brave
Who can tell me how I should behave
When I am disgraced
Because I erased
A file I intended to save?
Eduardo M KALINOWSKI
[EMAIL PROTECTED]
http://move.to/hpkb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
