sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:
But now you're making the assumption that machines of different
architectures see different contents in the same directory (or rather,
a different directory of the same name).
yes.
This suggests consistency where there is none. (At least the system
can't
enforce or even check it.)
Actually, it can because for instance the other /usr/local/libexec
directories are visible through an indirect path like
/net/the_other_machine/usr/local/libexec.
Note also that now uninstalling a package is a real bitch since
there
potentially isn't even a machine that sees all the bits of it, at
least definitely not in the obvious places.
Not in the obvious places, right. However, when you install a package
that needs compiling on different architectures, you'll make the compilation
twice, once on each architecture. It's not much more difficult to uninstall
twice. I admit you can reach an inconsistent state if for instance you
uninstall only on one machine. In that case, you'll have removed the share/
part for all architectures, but not all the libexec/ parts. That's the
sysadmin's fault though.
--
/ / _ _ 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