Re: native packages
On 1/23/07, George Danchev <email@example.com> wrote:
Right. Another disadvantage of making it a native package is that the
orig.tar.gz (imagine monsters here, ... OpenOffice.org comes to mind ;-) has
to be uploaded every time you change something in the package, even if this
is a change specific to the debianisation process, and no new upstream
version has been released. OTOH, having a debian_revision (i.e. a non-native
package), when you change something to the debianisation process and create a
new package with an increased debian revision number, you only need to upload
the diff.gz to the Debian archive.
Yes, and because of this we should avoid native packages as much as
possible. Nowadays, even projects with only one developer are stored
in revision-control-systems and hosted online.
So, it doesn't matter if something was written specifically for
Debian, you can still host the source and publish releases in alioth,
and by not having a native package allow debian-revision changes
without a full upload of the source.
Native packages are generally a bad idea. Please don't use them
unless you really know what you are doing.