Le 07/03/2012 09:14, Goswin von Brederlow a écrit : > I really don't get that argument. Nothing in having a debian directory > in the source hinders any other distribution. And plenty of sources > contain spec files for building rpms to no detriment to Debian. If any > non rpm based distribution picks up libaio-ocaml then I will be happy to > include their specs file too. Nothing is limiting the package to just > Debian there.
I am not against offering, as an upstream, Debian and RPM packaging information (in the VCS, for example), but I do believe the debian/ and $pkg.spec files (or e.g. scripts to make Mac OS X packages) do not belong to an official release tarball. The reason is that a change in debian/ or $pkg.spec might not be relevant to make a new upstream release. Besides, in the Debian case, there are NMUs and team uploads that are supposed to touch only stuff in debian/, and for something not related to Debian at all such as libaio-ocaml, it doesn't look right to me to make what technically qualifies as a "new upstream release" at each NMU... > With a moments thought I would have 3 branches: > - master > - upstream > - pristine-tar > > All developement would happen in the master branch. Then before the > Debian upload I would merge master -> upstream (excluding the debian > dir), roll an orig.tar from upstream and import that into the > pristine-tar branch, tag everything and finally build a non-native > package. This could all be done with a "make release" so it would be > effortless. Looks fine. I even suggest for yourself to merge master -> upstream before an upload only when there is an actual upstream change, and bump the upstream version number (and upload a new tarball to ocamlforge) only at this time. -- Stéphane -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f572679.8060...@debian.org
