Date: Tue, 18 Apr 1995 20:45:31 +0100 From: "wmbfmk@urc.tue.nl" <wmbfmk@urc.tue.nl> To: ports@FreeBSD.org Cc: asami@cs.berkeley.edu (Satoshi Asami), Travis L Priest <T.L.Priest@LaRC.NASA.GOV>, branson@dvals1.larc.nasa.gov, Tad Guy <E.E.Guy@LaRC.NASA.GOV> Subject: Re: Ports hackers wanted! (fwd) Message-ID: <199504181945.UAA16150@nietzsche>
next in thread | raw e-mail | index | archive | help
[ a lot of stuff about new package scheme deleted ] > 4 WHAT ARE THE ADVANTAGES OF USING THESE 'STANDARDS' > > This has turned out to have more advantages than we originally > anticipated. I'll enumerate: > > * A package is now a well-formed collection of files under a common > directory (/usr/local/pkg-rev). > > * You no longer have files belonging to one package in directories > where the vendor OS is installed, so it is less likely to be deleted > or modified when you perform an OS upgrade. In light of this, I would like to see our X-packages go into a seperate /usr/local/X11 tree. I don't want to reinstall all X-packages when I upgrade my /usr/X11R6 tree, everytime a new XFree86. I have been running this way for some time now, and I can even have the applications defaults files in the /usr/local/X11 tree by setting an environment variable: XAPPLRESDIR=/usr/local/X11/lib/X11/app-defaults This way all files for an X-package can go into the seperate tree. If we can't provide an upgrade-kit from version to version we could at least try to make it as easy as possible. Marc. Marc van Kempen wmbfmk@urc.tue.nl He's dead Jim ..., kick him if you don't believe me.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504181945.UAA16150>