On Mon, 2007-10-15 at 01:01 -0700, Donnie Berkholz wrote:
> On 09:56 Mon 15 Oct , Bo Ørsted Andresen wrote:
> > Written like this u certainly can't since the output of the find expression
> > is
> > subjected to word splitting before u gets set. Hence this will fail if ${D}
> > contains spaces even if ${u} gets quoted. The best way to solve this is to
> > use
> > find ... -print0 | xargs -0 rm. Unfortunately that solution means using GNU
> > extensions that I'm not sure are guaranteed to be available in the ebuild
> > environment. If they aren't maybe they should be.
>
> Cool, I hadn't dealt with this before. Thanks for pointing that out! We
> were just talking about whether to require GNU find the other day, but I
> don't recall the conclusion. Does anyone else?
I think most people wanted to force all GNU tools.
So once it's all keyworded BSD and installed outside of our normal $PATH
or g prefixed (gfind, gsed, etc) then you can start
DEPEND="your-find-of-choice" and use it in the ebuild.
But we're not there yet so lets use something that all platforms
support. Like say find's -delete action which should fit the bill quite
nicely.
Thanks
Roy
--
[EMAIL PROTECTED] mailing list
