The build-essential package has a very specific purpose defined by the
policy manual:
It is not necessary to explicitly specify build-time relationships on
a minimal set of packages that are always needed to compile, link and
put in a Debian package a standard "Hello World!" program written in C
or C++. The required packages are called build-essential, and an
informational list can be found in /usr/share/doc/build-essential/list
(which is contained in the build-essential package).
For everything else, packages with such configure scripts should build-
depend on gettext. build-essential's purpose is definitely not to
aggregate everything that configure scripts might need but fail to
detect properly, nor to work around bugs in configure scripts.
I'd argue that those Makefiles should not be failing like that if a tool
they need doesn't exist; either configure should bail out with a more
helpful message, or the Makefile should issue a more helpful message
itself. I think it's gettext that generates those, so I'll reassign this
over there. (It would have to be fixed upstream in order to be effective
for most projects.)
** Changed in: build-essential (Ubuntu)
Status: Triaged => Won't Fix
** Also affects: gettext (Ubuntu)
Importance: Undecided
Status: New
--
gettext should be in build-essential
https://bugs.launchpad.net/bugs/227163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
