🚀 go-pugleaf

>>>>> On 16 Mar 92 12:01:01 GMT, mhiroshi@tansei.cc.u-tokyo.ac.jp (mhiroshi) said:

> 1) The base path should be "/usr/gnu" like "/usr/ucb"
>    rather than "/usr/local" since GNU's software is not
>    just PDS but is Free Software that has different copyright(copyleft)
>    policy than the others.

'local' != 'pds'

> 2) Unifying the base path above (not under /usr/local )
>    greatly reduces the user's complication about the maintainance
>    of the GNU software.

> 3) The other idea is that all the programs are made so that
> it refers the user's environment variable as the base directory
> of the GNU products. For example if the environment variable
> GNUPATH is set to /usr/gnu, then everything is relative to that
> path. If the GNUPATH is set to /usr/local, then ... so on.
> However I think floating path is not as good as it sounds.

> How do you think?

#define FLAME_RETARDANT_PANCHO

Rule #1 from kjj's_sysadmin_manifesto_for_developers:
	Keep your poop out of other people's poop.
	You won't stomp on them and they won't stomp on you.
	Ie. contain your package in a single (?) directory tree.
	If you can't contain it in one single directory tree,
	then design it so that it can coexist with other packages
	in a /usr/local/{bin|lib|include|etc|man} type of architecture.

Rule #2 from kjj's_sysadmin_manifesto_for_developers:
	ALWAYS allow the sysadmin to relocate the base directory
	for a package!!!  Anything less is fascist.

#undef FLAME_RETARANT_PANCHO

As a sysadmin, most of the problems with 'packages' have been with
ones that violate these two 'rules'.

--
#include <std_disclaimer>
"If it runs GNUemacs it's a computer, otherwise it's a peripheral." - me
"I have two kitchen sinks: emacs and perl" - me
.-----------------------------------------------------------------------------.
| Kevin Johnson          kjj@phx.mcd.mot.com | ...!asuvax!mcdphx!pondscum!kjj |
| Information Technologies System Administrator  Motorola MCG                 |