General remark: I suspect lots of recipes depend on perl if only in their configure scripts. I guess doing per-patckage staging could improve the visibility of this.
Also wrt /usr/bin/env perl: I haven't peeked into the source of env, but ideally non-native recipes should maybe not rely on host packages, only on the ones we build. E.g. no /usr/bin in PATH wehn building these (and yes, I know that is not trivial and will trigger some bugs and it also does not help against hard coded paths, and probalby some progs will cause a pain (e.g. /bin/sh)). Maybe a chrooted system would be better, but I vaguely recall that this was once discussed (and presumably rejected). Another thing we could do is have our own env program which (in this case) does not return a path to perl if the native package is not there (and thereby causing things to fail instead of silently using the host perl). Have fun! Frans.
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
