On Sun, Dec 25, 2005 at 09:39:45PM -0800, Robin H. Johnson wrote:
> On Sun, Dec 25, 2005 at 07:41:01PM -0800, Brian Harring wrote:
> > On Sun, Dec 25, 2005 at 06:48:02PM -0500, Mike Frysinger wrote:
> > > On Sunday 25 December 2005 17:12, Brian Harring wrote:
> > > > Can be defeated by a unpack ${DISTDIR}/file call, but that's invalid
> > > > anyways.
> > >
> > > and what about things that do `cp ${DISTDIR}/aadsfasdf ${S}/` ? those
> > > are
> > > going to fail to wont they ?
> > Had originally thought about resetting DISTDIR to the symlink dir; it
> > would address this concern.
> Definetly change DISTDIR to point to the symlink dir.
>
> There were user-authored patches around more than year ago that
> implemented this (a dir containing symlinks to the real files), as part
> of somebodies multiple-distdir support.
Haven't seen them, but the original implementation that got tagged
into saviour was based on discussions/suggestions from you...Multiple distdir is a bit closer via this, but it still requires a lot of python side portage.fetch work to get there... Meanwhile, tagging this beast into trunk. ~harring
pgpcAhoITHApq.pgp
Description: PGP signature
