public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Master plan for fixing elibtoolize
Date: Fri, 17 Mar 2017 18:17:52 +0100	[thread overview]
Message-ID: <20170317181752.02cca84f@gentoo.org> (raw)
In-Reply-To: <1489770852.1490.6.camel@gentoo.org>

On Fri, 17 Mar 2017 18:14:12 +0100
Michał Górny <mgorny@gentoo.org> wrote:

> Hi, everyone.
> 
> Since the bug about libtool.eclass [1] has not received any
> attention, I hereby declare maintainer timeout and start working on
> improving the eclass.
> 
> The main goals are to:
> 
> a. stop requiring every single autoconf ebuild to call elibtoolize
> manually (and effectively having half-'broken' repository),
> 
> b. stop bundling the large number of patches with the repository,
> 
> c. stop using hacks to find those patches.
> 
> The planned steps are to:
> 
> 1. split epunt_cxx out of eutils:
> 
> 1.1. split the function into new eclass (PATCH already sent),
> 
> 1.2. explicitly inherit the new eclass in all ebuilds using epunt_cxx,
> 
> 1.3. remove implicit inherit from eutils,
> 
> 1.4. move patches to a package and make the new eclass DEPEND on it.
> 
> 2. move patches to a package and make libtool.eclass DEPEND on it.
> 
> 3. copy elibtoolize logic to Portage, and make it apply implicitly
> on econf [do we need to apply it elsewhere?]; disable explicit
> libtoolize when Portage supports that.


Define it in a new EAPI. Make elibtoolize die in EAPI supporting
auto-elibtoolize.


  reply	other threads:[~2017-03-17 17:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17 17:14 [gentoo-dev] [RFC] Master plan for fixing elibtoolize Michał Górny
2017-03-17 17:17 ` Alexis Ballier [this message]
2017-03-17 23:38 ` James Le Cuirot
2017-03-18  6:53   ` Michał Górny
2017-03-18 10:18     ` Alexis Ballier
2017-03-18 10:21       ` Michał Górny
2017-03-18 10:31         ` Alexis Ballier
2017-03-18 19:29           ` Peter Stuge
2017-03-22  9:38             ` Alexis Ballier

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=20170317181752.02cca84f@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