From: Doug Goldstein <cardoe@gentoo.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] epatch_user usage
Date: Mon, 23 Apr 2012 23:33:02 -0500 [thread overview]
Message-ID: <CAFWqQMQELCy-kw76ZQ0fWK9BBOQu5Nj0cnEVXipaw4_kM3zjcw@mail.gmail.com> (raw)
In-Reply-To: <201204240010.31805.vapier@gentoo.org>
On Mon, Apr 23, 2012 at 11:10 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Monday 23 April 2012 23:45:36 Doug Goldstein 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?
>
> just always call it when the user applies patches. i don't see a big deal.
> epatch_user && eautoreconf
> -mike
That works. I was wondering if you guys did anything more crafty but
this is fine.
Thanks all for the input.
--
Doug Goldstein
next prev parent reply other threads:[~2012-04-24 4:33 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
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 [this message]
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=CAFWqQMQELCy-kw76ZQ0fWK9BBOQu5Nj0cnEVXipaw4_kM3zjcw@mail.gmail.com \
--to=cardoe@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=vapier@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