--On Saturday, December 10, 2005 12:45 PM -0600 David Summers
<david@summersoft.fay.ar.us> wrote:
>> Ideally a single spec file exists in the tarball, so that one can just
>> recreate the package from the tarball with "rpmbuild -ta". That requires
>> that one use distro detection within the spec file to handle the
>> differences. That should also make it easier to maintain the spec files
>> and keep the common parts in sync. (RHEL 3 and 4 seem to differ
>> primarily in the versioned python directory name, 2.2 versus 2.3. Put
>> that in a macro at the top and the rest of the file should be almost
>> identical.)
>
> That would be great. Patches greatly welcome, or describe to me how that
> could be done and I'll work on it.
I asked on the RPM list:
<https://lists.dulug.duke.edu/pipermail/rpm-devel/2005-December/000627.html>
But after thinking about this more, I think the main difference is in
either names that can be passed on the rpmbuild command line (like the
distro name) or which dependent packages are used (eg. Python 2.2 versus
2.3). The latter should be detected at packaging time, since one might have
upgraded that package and the distro-based assumption would not be valid.
For filenames that end up in the %files list, one can dynamically generate
that list and pass it on the %files line. I've seen this done with Perl
packages, where the Perl version is encoded in the root of the library tree.
I'll look some more at the different spec files to see if I can generate a
patch to get some of the differences to be decided at packaging time.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 13 07:23:18 2005