public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: cardoe@gentoo.org
Subject: Re: [gentoo-dev] epatch_user usage
Date: Tue, 24 Apr 2012 06:05:32 +0200	[thread overview]
Message-ID: <20120424060532.3a566737@pomiocik.lan> (raw)
In-Reply-To: <CAFWqQMRpR9wHD8o5KygqtkzT9MJYUV_Ug_1GC58VYVFtrkLrkA@mail.gmail.com>

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

On Mon, 23 Apr 2012 22:45:36 -0500
Doug Goldstein <cardoe@gentoo.org> wrote:

> So I've just had one reservation when using epatch_user for allowing
> users to apply patches. And that's figuring out when to run
> eautoreconf. I don't necessarily want to run it unconditionally but
> sometimes users have patches which touch autoconf files but my
> existing patch set doesn't so I'm not calling eautoreconf. Does anyone
> have a suggested way to handle this?

inherit autotools-utils

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  parent reply	other threads:[~2012-04-24  4:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24  3:45 [gentoo-dev] epatch_user usage Doug Goldstein
2012-04-24  3:57 ` Arun Raghavan
2012-04-24  4:05 ` Michał Górny [this message]
2012-04-24  4:14   ` Alexandre Rostovtsev
2012-04-24  4:18     ` Michał Górny
2012-04-24  4:27       ` Mike Frysinger
2012-04-24  4:10 ` Mike Frysinger
2012-04-24  4:15   ` Michał Górny
2012-04-24  4:25     ` Mike Frysinger
2012-04-24  8:35       ` Michał Górny
2012-04-24  4:33   ` Doug Goldstein
2012-04-26  4:45 ` [gentoo-dev] " Ryan Hill
2012-04-26  5:06   ` Zac Medico
2012-05-04  4:50     ` Jeroen Roovers
2012-05-04 20:23       ` Michał Górny
2012-05-05  6:01         ` Ryan Hill

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=20120424060532.3a566737@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=cardoe@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