🚀 go-pugleaf

In article <122094@lll-winken.LLNL.GOV> sowa@amdew.llnl.gov writes:
>While I'm at it, why not point out an official NeXT inconsistency with
>this scheme? Why does Installer put third-party package files into
>/NextLibrary/Packages instead of, say, /LocalLibrary/Packages? OK, the
>relevant directory must be world-writeable, but if they shipped with the
>/Local... directories already made, this would be no more of a problem
>than the current situation. Yeah, it's a small thing, I know. I would
>also prefer that /NextLibrary/TeX go in the local hierarchy, too, since
>TeX is shipped uninstalled.

I agree with your position here.  In fact, I replace 
	/NextLibrary/Packages/ThirdParty
with a symbolic link pointing to
	/LocalLibrary/Packages/ThirdParty

One other comment on disk management schemes.  Since I have large (1.4GB)
disk, and I wanted to keep the NeXT supplied stuff in its own partition,
I have created a second partition on my disk that I mount as /local.
(I also have a partition called /home with all user accounts but that's
a different matter).  As to /local, I add the following symbolic links
on top of the NeXT OS partition so that these are the only things that
have to be updated if I wipe out or update the OS system:

	/usr/local		--> /local
	/LocalApps		--> /local/Apps
	/LocalLibrary		--> /local/Library
and of course
	/NextLibrary/Packages/ThirdParty --> /LocalLibrary/Packages/ThirdParty

Hope this is useful.  Comments are certainly welcome.

--Marc Ullman
  Stanford University