Sean Whitton <spwhit...@spwhitton.name> writes:
> There seem to be two schools of thought here: > > - native packages are to be used when the package's release process is > uploading to Debian unstable Well, that's reasonably convincing, despite being unsupported by policy ;). >> I don't propose to have seperate upstream repos, only branches. > > Even if Nick goes with non-native I think this is overkill. You can > just use a single branch containing both 1.2.3 and debian/1.2.3-1 > release tags. Downstreams can just ignore the debian/ dir. See > https://git.spwhitton.name/git-remote-gcrypt for an example of this. This is pretty much what notmuch does as well (with 1.2.3-2 effectively a point release with selective distribution). The argument gets a bit circular here. Branches make sense if you think separete upstream releases on MELPA make sense. I guess we could ask the perl people what there experience of releasing Debian-ish things on CPAN is. d
