On Sun, 04 Feb 2001, Adrian Bunk wrote:
> I have with Siggi Langauf (the maintainer of xine) a discussion in bug
> #84754 whether xine is a Debian native package or not.
We've discussed something like this in -policy recently.
Basically, here's the guidelines you should follow to decide wether you
should have a package be debian-native or non-native (all IMHO):
1. Are you likely to do small revisions that only affect the debian/
subdir, and the source package is big ?
-> if yes, choose non-native, because you'll not need to reupload
the .orig.tar.gz file, just the diff, dsc and changes file.
2. Are you likely to do small revisions that only affect the debian/
subdir, and the source package is small ?
-> if yes, do as you wish. But be warned that I'll be proposing in policy
that *SOURCE* (not binary) native packages be forbidden debian revision
fields (there's a good reason for that, see thread in -policy).
For small source files, you should use native if you don't mind
increasing the upstream release number just because of a change in
debian/, otherwise, go with non-native.
Native is best choosen for packages which are not expected to be used
outside of Debian, btw. If I were xine's upstream, I'd package it as
non-native. The non-native format is more flexible.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
Attachment:
pgp5aIKTAyMXE.pgp
Description: PGP signature