From: Chris Wright Date: Mon, 02 May 2005 19:08:52 GMT Subject: Re: [PATCH] add git.spec and adapt Makefile for RPM build Message-ID: <20050502190852.GH18917@shell0.pdx.osdl.net> In-Reply-To: <200505021858.j42Iw4M1029427@laptop11.inf.utfsm.cl> * Horst von Brand (vonbrand@inf.utfsm.cl) wrote: > Chris Wright said: > > It simply means a structured release process. IOW, > > the git.spec would be generated for a release tarball. > > Come on, you have to fix the spec file for the changelog and version by > hand anyway, autoconfiscating it doesn't help one iota there. That's the point, you don't _have_ to do that. > And yes, I've seen quite a few packages autogenerating the spec file. As a > result, you /can't/ build the package from pristine sources, you have to > unpack and configure to get enough for building. For me that just isn't > acceptable, as it completely misses the point of RPM. > > (You can go "rpmbuild -ta whatever-2.3.1.tar.bz2" if the tarball is set up > correctly, your idea prevents that). You just place the generated spec file in a release tarball. IOW, your 'release' Makefile target depends on foo.spec, and creates a clean release tarball with all you need to do an -ta build. thanks, -chris