From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] autotools eclass - set default for WANT_AUTO*
Date: Sat, 6 Jan 2007 16:22:21 +0100 [thread overview]
Message-ID: <200701061622.32676@enterprise.flameeyes.is-a-geek.org> (raw)
In-Reply-To: <200701061210.33600.alonbl@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
On Saturday 06 January 2007 11:10, Alon Bar-Lev wrote:
> Is there any reason why not setting "latest" as default for WANT_AUTO*
> variables?
Because then stuff will "magically" work in stable, and break in ~arch, and
you won't know why it's happening.
Instead if you follow the procedure (set the variables) you know that you
asked for latest version, and you'll be able to check what the problem is.
Yes, I expect automake 1.11 to break even more, as they are coming around.
--
Diego "Flameeyes" Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ...
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-06 15:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 10:10 [gentoo-dev] autotools eclass - set default for WANT_AUTO* Alon Bar-Lev
2007-01-06 10:21 ` Mike Frysinger
2007-01-06 14:47 ` Kevin F. Quinn
2007-01-06 14:57 ` Alon Bar-Lev
2007-01-07 5:19 ` [gentoo-dev] " Steve Long
2007-01-06 15:41 ` [gentoo-dev] " Mike Frysinger
2007-01-06 15:22 ` Diego 'Flameeyes' Pettenò [this message]
2007-01-06 15:42 ` Mike Frysinger
2007-01-06 16:05 ` Diego 'Flameeyes' Pettenò
2007-01-06 17:25 ` Mike Frysinger
2007-01-06 18:00 ` Diego 'Flameeyes' Pettenò
2007-01-06 18:23 ` Mike Frysinger
2007-01-06 18:32 ` Diego 'Flameeyes' Pettenò
2007-01-07 1:29 ` Mike Frysinger
2007-01-07 16:27 ` Alon Bar-Lev
2007-01-12 18:14 ` Mike Frysinger
2007-01-12 18:37 ` Alon Bar-Lev
2007-01-12 18:49 ` Mike Frysinger
2007-01-12 18:39 ` Mike Frysinger
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=200701061622.32676@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@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