-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 7 Jul 2001, Stefan van der Eijk wrote:
>>[compiling Cooker from scratch, installing only the BuildRequires
>>packages as needed]
>>>How are you detecting problems caused by 'non-fatal' missing
>>>BuildRequires? As an example: the recent missing requirement for
>>>libbzip2_1-devel and libtiff3-devel in kdelibs. If these are not
>>>installed then the package will be built without support for the relevant
>>>components, but no errors will be flagged.
>>It would be nice if autoconf's configure scripts allowed you to say:
>>
>>% ./configure --definitely-use-libtiff
>
>Then the developer would need to put that in the .spec file
>Why not then put in a BuildRequires libtiff-devel?
Ah. So this isn't the answer. But how about:
% ./configure
-
--definitely-use-everything-possible-including-the-kitchen-sink-and-die-if-it-is-not-there
(Fortunately, GNU tools allow you to abbreviate long options.)
This would make sure that anything that could be compiled in, is
compiled in. A real pain if you're trying to build XEmacs on say
Solaris, but useful for the RPM developer (and not a real burden for the
user, since dependencies can be dealt with for you).
You could override this option:
% ./configure --definitely-use-everything --no-libtiff
Then you explicitly have to ask for certain things to be skipped if you
know you're not using them. But they won't just silently fail. (Well,
it's pretty much 'silently' since the warning messages get lost in the
noise of messages from configure, make and rpm.)
- --
Ed Avis <[EMAIL PROTECTED]>
Finger for PGP key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7R3K6IMp73jhGogoRAm3AAJ4+tbLBdoYyZ8XD11BmJ28UUtOFWQCePnKg
QpUKmiJpP3DvqjdSxmQKIHQ=
=sfy4
-----END PGP SIGNATURE-----
