On Tuesday, 28 March 2006 at 19:52, Andreas Metzler wrote:
> why is this severity important, sounds like wishlist to me.
Well, maybe 'important' is too high, but I don't think 'wishlist' really
fits. I have tried to compile a program (the cvs version of cegui) where
./configure checks for libpcre via pkg-config, and doesn't find it, even
after installing the elevopment package. I have manually copied the .pc
file and everything works.
Now what will someone do who doesn't know how to investigate a failed
./configure run? In my opinion this fits the description of 'important'
("a bug which has a major effect on the usability of a package, without
rendering it completely unusable to everyone"), depending on the
definition of 'major'.
> Is it actually a good thing to ship the pc-file, therefore suggesting
> to actually use pkg-config for finding pcre? We have done well
> without using it for pcre for three major releases, and I seem to
> recall that pkg-config is still a major source for unneeded linking
> against indirect dependencies, mainly due to #340904.
I guess that's more for debian-devel, I only know that there are
programs that check for libpcre via pkg-config.
Christian Ohm
--
Never go to a doctor whose office plants have died.
-- Erma Bombeck
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
