public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@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 13:08:19 -0500	[thread overview]
Message-ID: <20170611180819.GA4134@linux1> (raw)
In-Reply-To: <1497197692.24558.5.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]

On Sun, Jun 11, 2017 at 07:14:52PM +0300, Mart Raudsepp wrote:
> Ühel kenal päeval, P, 11.06.2017 kell 11:12, kirjutas William Hubbs:
> > On Sun, Jun 11, 2017 at 05:35:53PM +0200, Kristian Fiskerstrand
> > wrote:
> > > On 06/11/2017 05:24 PM, David Seifert 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.
> > > > > 
> > > > 
> > > > Here's a deal: you can start filing + fixing them.
> > > > 
> > > 
> > > The [tracker] is already started, it was determined to add QA
> > > warning
> > > with info on filing upstream bugs in [bug 426262] and the proper
> > > solution is again iterated in [bug 546614], so its not like this is
> > > a
> > > new approach that is being suggested, but sure, we should all file
> > > bugs
> > > when we encounter them.
> > > 
> > > References:
> > > [tracker] https://bugs.gentoo.org/show_bug.cgi?id=530632
> > > 
> > > [bug 426262]
> > > https://bugs.gentoo.org/show_bug.cgi?id=426262
> > > 
> > > [bug 546614]
> > > https://bugs.gentoo.org/show_bug.cgi?id=546614
> > 
> > It seems that the proper fix to this, even for a package that won't
> > do
> > the fix upstream is to use WANT_AUTOCONF in the ebuild to force the
> > version of autoconf you need.
> 
> No. It appears you don't know how WANT_AUTOCONF works.
 
 From the eclass:

# @ECLASS-VARIABLE: WANT_AUTOCONF
# @DESCRIPTION:
# The major version of autoconf your package needs

That leads me to believe that you can set WANT_AUTOCONF="someversion"
in your ebuild and your package will use that version of autoconf.

If that's wrong, it needs to be fixed and that's a different bug
entirely, but it doesn't change my position on adding this particular
change to autotools.eclass.

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-06-11 18:08 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
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 [this message]
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=20170611180819.GA4134@linux1 \
    --to=williamh@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