From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Why autoconf in system?
Date: Mon, 12 Sep 2005 14:40:42 +0200 [thread overview]
Message-ID: <1126528842.14207.51.camel@lycan.lan> (raw)
In-Reply-To: <1126527993.5947.159.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On Mon, 2005-09-12 at 14:26 +0200, Frank Schafer wrote:
> Hi,
>
> we meet often the (faulty) notion that autoconf/automake (even a couple
> of versions on gentoo) is a dependency for packages.
>
> This is true only for development of these packages itself.
> Autoconf/automake provides tools to GENERATE configure scripts. Both are
> totally unnecessary to build a package or run the programs it provides.
> I've built a full featured LFS system not long ago without even
> autoconf/automake installed.
>
> I'd suggest to remove the build of autoconf/automake from ``emerge
> system''. I'd leave all of the autoconf/automake versions in portage
> tough for the case someone wants to involve in development of some
> package.
>
While this is true, you missed the fact that many packages from time to
time apply patches that touches configure.{ac,in}, or Makefile.am, or
just do not come tarballed with configure, etc generated, so it is
indeed needed.
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-12 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 12:26 [gentoo-dev] Why autoconf in system? Frank Schafer
2005-09-12 12:38 ` Paul de Vrieze
2005-09-12 12:40 ` Martin Schlemmer [this message]
2005-09-12 12:41 ` Mike Frysinger
2005-09-12 12:48 ` Frank Schafer
2005-09-12 12:56 ` Mike Frysinger
2005-09-12 12:58 ` Stephen P. Becker
2005-09-12 14:38 ` Mike Frysinger
2005-09-12 16:06 ` Martin Schlemmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1126528842.14207.51.camel@lycan.lan \
--to=azarah@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox