Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Mar 1995 22:54:04 -0800
From:      asami@cs.berkeley.edu (Satoshi Asami/=?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=)
To:        mark@grondar.za
Cc:        ports@FreeBSD.org
Subject:   Re: Gripe of the week (tm) :-)
Message-ID:  <199503210654.WAA08178@silvia.HIP.Berkeley.EDU>
In-Reply-To: <199503201818.UAA28034@grunt.grondar.za> (message from Mark Murray on Mon, 20 Mar 1995 20:18:55 %2B0200)

next in thread | previous in thread | raw e-mail | index | archive | help
 * Sure. It is possible to go _crazy_ and do what you like with these
 * symlinks, but life gets awfully messy. Lets just do it _right_.

Well, I might be CRAZY (*-_-*) but I thought this, although it might
be wrong, was the only way to solve the problem entirely within the X
tree.  I didn't like having two separate bin dirs, man dirs, etc.  It
will clutter up my PATH, /etc/manpath.config, /etc/weekly, among other
things.

 * It is very manual. With a clear separation of the two trees, and a _known_
 * grey area (app-defaults) (which is kinda-like /etc in that it contains all
 * your local setups, kluges, preferences etc, no?), surely life will be a lot
 * easier?

Actually the whole lib/ subdirectory and much of include/ is a gray
zone.  (bin/ and man/ aren't that difficult to separate.)  Don't
forget that X programs often want to install their own libraries
and/or header files, and the imake system just isn't prepared to deal
with two sets of these.  They think where you install = where you find
libs/includes.

So you either fix things with symlinks like I said, or as Rod
suggested, go the imake config way.  The latter is much better and is
the "real" solution but it takes time and we need to cooperate with
the XFree86/X Consortium people...the former is, well, dirty and
"incorrect" but at least gives you the illusion of having a "standard"
X tree (very important to do port works) with minimal effort during
upgrades.

Maintaining the symlink tree isn't all that bad, as "colorls -GR |
colorless" can tell me about all the bogus symlinks.  For the new
files, I just run the setup script again, it will fail when the link
is already there.

Satoshi



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503210654.WAA08178>