From: David Seifert <soap@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:24:31 +0200 [thread overview]
Message-ID: <1497194671.30990.8.camel@gentoo.org> (raw)
In-Reply-To: <ca2e4823-c58e-3155-3652-6b88b0adbf1f@gentoo.org>
On Sun, 2017-06-11 at 17:12 +0200, Kristian Fiskerstrand wrote:
> On 06/11/2017 05:07 PM, Mart Raudsepp wrote:
> > Ühel kenal päeval, P, 11.06.2017 kell 10:00, kirjutas William
> > Hubbs:
> > > On Sat, Jun 10, 2017 at 01:04:06PM +0100, Sergei Trofimovich
> > > wrote:
> > > > On Sat, 10 Jun 2017 13:28:19 +0200
> > > > Jeroen Roovers <jer@gentoo.org> wrote:
> > > >
> > > > > https://bugs.gentoo.org/show_bug.cgi?id=426262
> > > > > + mv configure.{in,ac} || die
> > > >
> > > > Looks good.
> > > >
> > > > --
> > > >
> > > > Sergei
> > >
> > > -1
> > >
> > > I think this should be handled by the packages, not at the eclass
> > > level.
> > >
> > > https://bugs.gentoo.org/show_bug.cgi?id=426262#c3
> > >
> > > The packages should either mv the configure.in to configure.ac
> > > internally, or better yet, the maintainers should ask upstream
> > > for
> > > their
> > > packages to fix it.
> >
> > +1, otherwise we will never be able to add/unmask a newer autoconf
> > that
> > doesn't look at configure.in anymore, once such a version
> > eventually
> > happens.
> >
>
> 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.
>
Here's a deal: you can start filing + fixing them.
David
next prev parent reply other threads:[~2017-06-11 15:24 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
2017-06-11 15:24 ` David Seifert [this message]
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=1497194671.30990.8.camel@gentoo.org \
--to=soap@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