On May 8, 2009, at 4:35 AM, devzero2000 wrote:

> OK. Got the point.
>

So (because the solution for paths is obvious and simple) I've
added bin/ and lib/ directories to /usr/lib/rpm, and install
the JS shell in bin/js, and the JS bindings for RPM in lib/libjsm.so.

That solution should surprise noone, is entirely consistent with
existing practice like /opt/APPLICATION/{bin,lib}/, and solves
the tyranny of having to discuss and justtify each and every path used  
by
rpm to death for usage cases that may never be important.

For multilib, one can have /usr/{lib,lib64}/rpm multilib paths.
That's consistent with how many interpreters are providing multilib.

But I'm _SURE_ someone will find FHS flaws with the scheme. Isn't
it ironic that choices like "executables in bin/, libraries in lib/"
is somehow in need of discussion on uglix these days because of  
"standard"
carpet-baggers.

Now to figger how to use mount -bind (or FUSE) to propagate /usr/lib/ 
rpm/bin
into chroot's, and to permit relative paths like "sh" instead of
"/bin/sh" so that cross-packaging might be contemplated without
the rigors of switching everything to using embedded interpreters like  
lua.

73 de Jeff