sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:
The GNU standards impose one such ordering by having (I may be wrong
since
we don't use it) a share/ hierarchy and a lib/ or libexec/ hierarchy, deep
underneath which lie the architecture-dependent portions.
I think this is a misinterpretation (see below), but I also may be
wrong.
At least emacs-20.3 has, by default, the following
architecture-specific portions in its hierarchy:
bin/
libexec/emacs/20.3/<architecture>
This means that the architecture-specific parts of Emacs are spread
over two different hierarchies. It would make plenty of sense,
however, to mount the architecture-specific portions of a software
package only on the machines of that particular architecture.
Sure. Actually, I'm surprised that GNU Emacs has this layout. What we
do here is having /usr/local/bin and /usr/local/lib[exec] shared by all
identical machines. emacs-20.3 would then install in /usr/local/bin and
/usr/local/libexec/emacs/20.3/ <that's all> and you're done for all these
machines. If you want to compile it for other architectures, you just do it on
another machine, or cross-compile and install through the /net filesystem.
You see that I don't have to add any mountpoints or whatever. All
directories needed to be shared are already there.
--
/ / _ _ Didier Verna
http://www.inf.enst.fr/~verna/
- / / - / / /_/ / ENST, INFRES C201.1 mailto:vernaļ¼ inf.enst.fr
/_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46
75013 Paris, France Fax. +33 (1) 45 81 31 19