On Wed, Sep 02, 2009 at 07:09:01PM +0000, Sune Vuorela wrote: > >>From the changelog: > > > > * Upstream has abandoned the program, so the package is now Debian > > native. > > Switching upstreams does not make a package native.
How so? There is no reason why a package where the upstream and the Debian Developer are one and the same person could not be native. I know it is fancy and modern to think that Debian native packages should only be used for things that are specific to the Debian infrastructure, but there is nothing in policy that requires that, and indeed several packages (including, e.g., offlineimap) are distributed as such. Of course making a package Debian native can have downsides, and anyone considering doing so should weigh these downsides against the benefits that going native may or may not bring them; however, if they choose to do so, there is no reason for them not to do so. As it should be. -- The biometric identification system at the gates of the CIA headquarters works because there's a guard with a large gun making sure no one is trying to fool the system. http://www.schneier.com/blog/archives/2009/01/biometrics.html
signature.asc
Description: Digital signature
