Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!hsdndev!cmcl2!adm!fstc-chville.army.mil!root
From: root@fstc-chville.army.mil (Operator)
Newsgroups: comp.windows.open-look
Subject: Re: Openwin or X11R4
Keywords: OpenWin X11R4
Message-ID: <1991May31.122420.5070@fstc-chville.army.mil>
Date: 31 May 91 12:24:20 GMT
References: <1991May29.144727.5008@javelin.sim.es.com> <1991May29.230342.15836@ncs.dnd.ca>
Organization: US Army Foreign Science & Technology Center
Lines: 29

rpburry@ncs.dnd.ca (Paul Burry) writes:
>In article <1991May29.144727.5008@javelin.sim.es.com> bgeer%javelin@dsd.es.com writes:
>|shortly before the arrival of the IPC.  So far, I'm not that impressed
>|with openwin on the IPC, especially since the distribution of X
>|includes, libraries, & executables files are into non-X11-typical
>|subdirectories.  I mean, I don't think I should have to monkey around
>|with make files to compile such benign programs as xv or xroaches.

I agree...
I don't like the /usr/openwin stuff...    I want includes to be in /usr/include/X11
(not /usr/openwin/include/X11) and I want binaries in /usr/bin (not /usr/openwin/bin)
etc...   So I just:
1) tar /usr/openwin into a file
2) cd /usr and untar the file...
3) rm -r /usr/openwin

That solves 99% of the problems...   No FONTPATH, MANPATH, LD_LIBRARY_PATH,
etc to mess with...


Regarding the openwin fonts...   I think they are great...   Much better than the
MIT fonts...   I have had very little trouble getting the MIT-developed clients
to port to Sun's OPENWIN...

And I think the olvwm is super...    I've used the MIT-X11 and I've used
OPENWIN...    I think OPENWIN on the Sun is much better supported...

Brian
boyter@fstc-chville.army.mil