-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 01 Oct 2003 15:34:32 -0400, Sean Middleditch wrote:
No, you need to actually do the work of the configure script (perhaps you should actually use the app's configure script) - detect the individual bits in the system. Otherwise your package is broken.
What you describe is a maintenance nightmare. Assume an application
wants aspell >= 0.50, but distribution B provides only aspell 0.30. A
versioned build requirement on aspell >= 0.50 won't suffice, because
the package won't build on B. But there is a configure switch to
disable aspell support. So, what we can do is either examine aspell
version somehow, e.g. with
$(rpm -q --qf "%{version}" aspell)
or check a file like redhat-release.
You're asking for completely generic rpms where the user, who has upgraded a component way beyond the version which was shipped with the original distribution, does not need to supply optional rpmbuild parameters (such as --define _with_aspell=1) for a src.rpm to build _with_ support for that optional component.