From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] autotools.eclass: automatically move configure.in to configure.ac
Date: Sun, 11 Jun 2017 17:36:26 +0200 [thread overview]
Message-ID: <20170611173626.7b1c087d@gentoo.org> (raw)
In-Reply-To: <8ae2c4f3-273a-429d-95b9-dd5fae537f46@gentoo.org>
On Sun, 11 Jun 2017 17:20:49 +0200
Kristian Fiskerstrand <k_f@gentoo.org> wrote:
> On 06/11/2017 05:17 PM, Mart Raudsepp wrote:
> >> We can always patch the eclass at that point if that is still a big
> >> concern, but I fundamentally agree with William on this, starting
> >> point
> >> should be fixing it upstream, so can start with a tracking bug on
> >> affected packages.
> > That's a complete useless waste of time, to track some ancient
> > packages that don't get any upstream update anyway. The active ones
> > have updated it long ago. And it'd be a joke to propose last riting
> > for the reason of a file being named configure.in instead of
> > configure.ac.
> >
> >
>
> That determination can be made on a package-by-package basis and fixed
> in ebuild if needed.
>
Funny thing is that packages still using autoconf 2.1* don't get
any warning and packages setting WANT_AUTOCONF to some older version
will never break...
next prev parent reply other threads:[~2017-06-11 15:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 11:28 [gentoo-dev] autotools.eclass: automatically move configure.in to configure.ac Jeroen Roovers
2017-06-10 12:04 ` Sergei Trofimovich
2017-06-11 15:00 ` William Hubbs
2017-06-11 15:07 ` Mart Raudsepp
2017-06-11 15:12 ` Kristian Fiskerstrand
2017-06-11 15:17 ` Mart Raudsepp
2017-06-11 15:20 ` Kristian Fiskerstrand
2017-06-11 15:36 ` Alexis Ballier [this message]
2017-06-11 15:24 ` David Seifert
2017-06-11 15:35 ` Kristian Fiskerstrand
2017-06-11 16:12 ` William Hubbs
2017-06-11 16:14 ` Mart Raudsepp
2017-06-11 18:08 ` William Hubbs
2017-06-11 20:02 ` Mart Raudsepp
2017-09-21 14:14 ` Ian Stakenvicius
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=20170611173626.7b1c087d@gentoo.org \
--to=aballier@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