Date: Wed, 19 Apr 1995 04:50:28 -0700 From: asami@cs.berkeley.edu (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=) To: wmbfmk@urc.tue.nl Cc: ports@FreeBSD.org, T.L.Priest@LaRC.NASA.GOV, branson@dvals1.larc.nasa.gov, E.E.Guy@LaRC.NASA.GOV Subject: Re: Ports hackers wanted! (fwd) Message-ID: <199504191150.EAA09504@silvia.HIP.Berkeley.EDU> In-Reply-To: <199504181945.UAA16150@nietzsche> (wmbfmk@urc.tue.nl)
next in thread | previous in thread | raw e-mail | index | archive | help
* 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'd love to see this too, but how is it going to work? Binaries are okay, but what's going to happen if your port has a library that it wants to install? Or a header file? The sad truth is, X's imake framework doesn't support a way for us to have two separate trees. Until that is fixed, there isn't much we can do about it. Of course, if someone (you? :) can dive into the imake config files and fix them to support this "system and application tree" paradigm, and submit it back to the X consortium, it would be great, and you'll be my hero. Meanwhile, you can just overwrite your /usr/X11R6 when you do an upgrade, 'cause that should only update the "system" files. This is what my roommates do, and it seems to work fairly well for them. * 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. Adding a "required" environment variable to the user's space is a bad idea, IMHO. XAPPLRESDIR should be left to the user in case she wants to put her own stuff in a different place. * If we can't provide an upgrade-kit from version to version we could * at least try to make it as easy as possible. If you really want to see the long and winding path I've taken on my system to separate the system and application stuff, dig in the mail archives, I wrote about my symlink tree a month or so ago. It works fairly well, but you probably need color_xterm and colorls (works very well to find dangling symlinks :). Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504191150.EAA09504>