| 1 |
On Sun, Dec 25, 2005 at 07:41:01PM -0800, Brian Harring wrote: |
| 2 |
> On Sun, Dec 25, 2005 at 06:48:02PM -0500, Mike Frysinger wrote: |
| 3 |
> > On Sunday 25 December 2005 17:12, Brian Harring wrote: |
| 4 |
> > > Can be defeated by a unpack ${DISTDIR}/file call, but that's invalid |
| 5 |
> > > anyways. |
| 6 |
> > |
| 7 |
> > and what about things that do `cp ${DISTDIR}/aadsfasdf ${S}/` ? those are |
| 8 |
> > going to fail to wont they ? |
| 9 |
> Had originally thought about resetting DISTDIR to the symlink dir; it |
| 10 |
> would address this concern. |
| 11 |
Definetly change DISTDIR to point to the symlink dir. |
| 12 |
|
| 13 |
There were user-authored patches around more than year ago that |
| 14 |
implemented this (a dir containing symlinks to the real files), as part |
| 15 |
of somebodies multiple-distdir support. |
| 16 |
|
| 17 |
-- |
| 18 |
Robin Hugh Johnson |
| 19 |
E-Mail : robbat2@g.o |
| 20 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives