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