On Thu, Oct 06, 2005 at 01:13:53AM +0100, Ciaran McCreesh wrote: > On Wed, 5 Oct 2005 18:40:46 -0500 Brian Harring <[EMAIL PROTECTED]> > wrote: > | > It does in some places, it doesn't in others. It especially doesn't > | > for things that aren't normally found via PATH. It's a hell of a > | > mess. > | > | Examples? > > Of stuff in PATH? /bin/sh is assumed throughout to be a Bourne > compatible shell (and SHELL and CONFIG_SHELL aren't universally > honoured). uname, hostname and sed are called with hard paths (with > various fallbacks) in several early on stages. Of stuff not in path? > There's no standard and widely used way of digging up where libexec > tools are. What's being raised here is issues with making ebuilds handle prefix _perfectly_. Where are the portage issues, so that people can actually jump in and start testing out actual solutions, rather then conjecturing about what may or may not break? ~harring
pgpvDKijE0RXh.pgp
Description: PGP signature
