From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] need for autotools
Date: Tue, 25 Oct 2016 11:35:28 -0400 [thread overview]
Message-ID: <01ee0bdf-a0a7-4485-0c34-096b5ebdfd37@gentoo.org> (raw)
In-Reply-To: <16eff12b-0a21-23aa-a829-f7531f593e3c@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1232 bytes --]
On 25/10/16 11:34 AM, Ian Stakenvicius wrote:
> On 25/10/16 11:05 AM, Nick Vinson wrote:
>> On 10/25/2016 07:11 AM, Raymond Jennings wrote:
>>> Don't you need autoconf and automake to build a lot of packages?
>>
>> Theoretically no. When autotools is used correctly, the release tarball
>> has no dependency on either. That said, many people don't generate /
>> distribute a release tarball.
>>
>> However, I don't think this is the criterion used to determine what
>> should be in @system. The wiki defines the system set as the set that
>> "contains the software packages required for a standard Gentoo Linux
>> installation to run properly".
>>
>> That definition definitely excludes automake and autoconf (arguably gcc
>> should also excluded, under that definition, so the wiki might not be
>> 100% correct).
>>
>> -Nicholas Vinson
>>
>
> Unless you need to patch the build system, in which case you need to
> re-run autoconf/automake/etc (usually via 'eautoreconf'). And there's
> -plenty- of instances of that around as well.
>
I forgot to mention that autotools.eclass brings in these dependencies
as-needed, though, so I agree that they definitely are not required in
the @system set.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2016-10-25 15:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 0:43 [gentoo-dev] Commented packages in the @system set Michael Orlitzky
2016-10-25 14:01 ` Alexis Ballier
2016-10-25 14:03 ` Kristian Fiskerstrand
2016-10-25 14:11 ` Raymond Jennings
2016-10-25 14:16 ` Alexis Ballier
2016-10-25 15:05 ` Nick Vinson
2016-10-25 15:34 ` [gentoo-dev] need for autotools (was: Commented packages in the @system set) Ian Stakenvicius
2016-10-25 15:35 ` Ian Stakenvicius [this message]
2016-10-25 15:41 ` [gentoo-dev] need for autotools Kristian Fiskerstrand
2016-10-25 15:47 ` [gentoo-dev] Commented packages in the @system set Mike Gilbert
2016-10-25 16:49 ` Michał Górny
2016-10-26 10:22 ` Raymond Jennings
2016-10-26 18:55 ` Peter Stuge
2016-10-25 16:27 ` Rich Freeman
2016-10-26 0:40 ` Benda Xu
2016-10-27 0:19 ` waltdnes
2016-10-27 1:10 ` Peter Stuge
2016-10-27 2:54 ` Walter Dnes
2016-10-27 3:14 ` Rich Freeman
2016-10-27 11:46 ` Michael Orlitzky
2016-10-27 13:07 ` Michael Mol
2016-10-27 13:21 ` Rich Freeman
2016-10-27 14:41 ` Michael Mol
2016-10-27 15:22 ` Rich Freeman
2016-10-28 1:27 ` Kent Fredric
2016-10-28 1:49 ` Rich Freeman
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=01ee0bdf-a0a7-4485-0c34-096b5ebdfd37@gentoo.org \
--to=axs@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