On Tue, Sep 20, 2011 at 11:05 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > On Tue, Sep 20, 2011 at 11:00:02PM +0200, Jerome Martin wrote: >> 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. > > I've always hated the targets as they contains all kinds of nasty > build system hacks. > > Just having a debian/ dir, and packagename.spec in the toplevel > directory seems a lot easier and allows dpkg-buildpackage and rpmbuild > to just work. Well, I understand. This is what you would get from the extracted tree if I did put the rpm + debian packaging files in the tarball. But in the git repo, I need targets for many reasons specific to my build environment, among those build farm scripts expecting a uniform output location for the packages no matter on which system the build occurs, the versioning being templated with the actual version string as git tags, etc. -- 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
