Adeodato Simó <[EMAIL PROTECTED]> writes: > * Russ Allbery [Wed, 26 Dec 2007 11:35:53 -0800]:
>> I also considered making several of the packages that I maintain >> native, since I keep the debian directory in the upstream VCS, but >> decided against it becaues of this, and also because Debian also often >> needs new releases that are meaningless for people outside of Debian. > I do the same, release as non-native. However, I do not think we should > mandate that everybody does the same, as other people may have different > views on what workflow works best for them. And it's not, after all, > such a big deal. I guess the only way it could be seriously confusing is that we've had some long-standing confusion over the correct version number for an NMU of a Debian-native package. Provided that NMUs of Debian-native packages append -0.1 to the version string, it should be fine; otherwise, we end up with a version in Debian that looks like the same versioning string that's used for the non-Debian release but isn't. NMUs of Debian-native packages with no existence outside of Debian don't have this problem since there's no other versioned release to be inconsistent with. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
