On Tue, Sep 20, 2011 at 7:15 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > On Tue, Sep 20, 2011 at 12:11:57PM +0200, Jerome Martin wrote: >> Would it be better for the distro maintainers to instead have a >> tarball generated without the RPM specfile, debian subdirectory and >> packaging targets (no Makefile), but instead just plain (versioned) >> sources and the setup.py as official upstream release means ? If so, I >> would just add along a "tarball" target to the existing Makefile and >> be done with it faster. > > A tarball should always be the canonical upstream release. I really > like it if it has proper autogenerated Debian and RPM packaging files, > though - that makes building the latest release a whole lot easier for > me. Mmmh. I am not sure why you specifically mention autogenerated debian/RPM packaging files. AAMOF, I started this way using python installer generated packaging info, but that was causing some flexibilty issues and what we currently have are ad hoc packaging files. Anyway, do you specifically need those in the release tarball, or having them in the git tree is enough ? I have two options: 1) Makefile in git tree with targets 'deb', 'rpm' and 'tarball' (with no packaging info in it) 2) Makefile in git tree with just 'tarball' target, and then you can directly use either dpkg-buildpackage or rpmbuild from the extracted tree. Even in case 2), I would keep 'deb' and 'rpm' targets anyway, putting the resulting packages under dist/ or build/, but this is somehow system-specific for rpm as the rpmbuild root seems to vary. > For RPM the spec has always been just a recommendation and rpm distro > packager could just ignore it. For Debian the debian/ dir traditionally > was a real pain, but apparently with the 3.0 format it's just fine, so > please keep it. Ok, you seem to suggest option 2) there, aka packaging files in the release tarball, and just have downstream maintainers ignore those. -- Jérôme Martin -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
