On Mon, Apr 03, 2006 at 04:42:18AM -0500, Peter Samuelson wrote:
> [Christian Ohm]
> > 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'.
> Just remember that every bug that hits *you* is important to *you*, and
> causes major usability effects for *you*. A good rule of thumb for
> filing bugs: think long and hard about what severity you think a bug
> warrants, then ignore your conclusion and leave it at "normal".
> In this case, the only way this bug would be 'important' would be if
> most people only use libpcre3-dev for compiling someone else's
> software, rather than for writing and developing their own. If you're
> writing your own software that uses pcre, obviously you'll know better
> than to rely on pkg-config to find every last library in the world.
> Even if you know that pcre is supposed to support pkg-config, it won't
> faze you much when Debian's happens not to.
Hrm? There's an awful lot of compiling of other people's software that gets
done with libpcre3-dev; I can name, oh, 114 or so pieces of software for
which this is the case.
If upstream provides a .pc file with the expectation that it be installed,
Debian fails to install it, and someone is trying to compile a third-party
application against libpcre3-dev that fails to build because this .pc file
is missing, that sounds pretty important to me. <shrug>
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature