On Fri, Sep 20, 2013 at 10:18:18AM -0400, Dave Steele wrote: > I'm not sure we are clear with terms here. The newbie is the upstream, > and he has chosen to include the debian directory in his main > repository. Should he choose to rev the packaging, upstream is > coordinated, by definition.
As such, a trivial debian package change would trigger a new upstream release. If this is the intent, that's fineish in my view, but remember, this screws up and chance of cross-distro work (since a change to RPM local stuff, as example, would trigger a new upstream, and a no change rebuild in Debian to match) I really discourage this usage a lot. Native packages must be for packages local to Debian only. > I'm good with the idea that using 'native' with non-native packages is > 'stupid'. My question was about resolving the definition of 'native'. > Shouldn't it simply mean that upstream is the Debian maintainer, and > that the packaging is included? That is the guidance I was given > regarding one of my packages. > > -- > "Le mieux est l'ennemi du bien" - Voltaire -- .''`. Paul Tagliamonte <paul...@debian.org> : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag
signature.asc
Description: Digital signature