| 1 |
On Tue, 24 Apr 2012 00:25:56 -0400 |
| 2 |
Mike Frysinger <vapier@g.o> wrote: |
| 3 |
|
| 4 |
> On Tuesday 24 April 2012 00:15:45 Michał Górny wrote: |
| 5 |
> > On Tue, 24 Apr 2012 00:10:30 -0400 Mike Frysinger wrote: |
| 6 |
> > > On Monday 23 April 2012 23:45:36 Doug Goldstein wrote: |
| 7 |
> > > > So I've just had one reservation when using epatch_user for |
| 8 |
> > > > allowing users to apply patches. And that's figuring out when |
| 9 |
> > > > to run eautoreconf. I don't necessarily want to run it |
| 10 |
> > > > unconditionally but sometimes users have patches which touch |
| 11 |
> > > > autoconf files but my existing patch set doesn't so I'm not |
| 12 |
> > > > calling eautoreconf. Does anyone have a suggested way to handle |
| 13 |
> > > > this? |
| 14 |
> > > |
| 15 |
> > > just always call it when the user applies patches. i don't see a |
| 16 |
> > > big deal. epatch_user && eautoreconf |
| 17 |
> > |
| 18 |
> > No configure.{ac,in} present! |
| 19 |
> |
| 20 |
> if the package doesn't have configure.{ac,in} files, then why would |
| 21 |
> he be talking about eautoreconf ? |
| 22 |
|
| 23 |
Ah, so we're talking per-package now. Sorry, thought it would be forced |
| 24 |
everywhere. |
| 25 |
|
| 26 |
-- |
| 27 |
Best regards, |
| 28 |
Michał Górny |
Archives