public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: David Seifert <soap@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] out-of-source.eclass: A new eclass to help with out-of-source builds
Date: Thu, 16 Nov 2017 14:54:46 +0100	[thread overview]
Message-ID: <1510840486.24883.0.camel@gentoo.org> (raw)
In-Reply-To: <20171116134818.13899-1-mgorny@gentoo.org>

On Thu, 2017-11-16 at 14:48 +0100, Michał Górny wrote:
> // NB: I'm not sure if I haven't submitted it already but that was
> // a long time ago, so let's try again. Requested by soap.
> 
> The out-of-source.eclass is a simple multilib-minimal-style wrapper
> to perform out of source builds of autotools (and other) packages. It
> is
> mostly derived from the function served in the past by autotools-
> utils
> since a number of developers found it useful. However, in order to
> avoid
> the mistakes of autotools-utils, it is meant to be focused on a
> single
> feature and have a better API.
> 
> This eclass has two use cases:
> 
> 1. Ensuring that packages are tested with out-of-source builds.
> 
> 2. Improving consistency between multilib and non-multilib packages.
> 
> In the most basic form, it just redefines the phases from
> src_configure()
> to src_install() with out-of-source wrappers. However, each phase can
> be overriden using my_src_*() sub-phase that is run inside build dir
> (alike multilib_src_*() in multilib-minimal). There is also
> my_src_install_all() for the trailing source-dir actions.

+1


  reply	other threads:[~2017-11-16 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 13:48 [gentoo-dev] [PATCH] out-of-source.eclass: A new eclass to help with out-of-source builds Michał Górny
2017-11-16 13:54 ` David Seifert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-08-12 22:23 Michał Górny

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=1510840486.24883.0.camel@gentoo.org \
    --to=soap@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@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