On Wed, Dec 12, 2001 at 07:48:45PM -0000, David Laight wrote:
> > > In the particular case of emacs, there's an option (-nw) that lets you
> > > tell it NOT to use X.  You could wrap emacs up in a script that invokes
> > > the real emacs with the option to disable using X.  (Also, if you link to
> > > the machine from a system that is running X, you might want to have X
> > > support there.  Something to think about before you disable it completely
> > > in your copy of emacs by rebuilding.  (^&)
> > 
> > bash-2.04$ emacs -nw
> > Shared object "libXaw.so.6" not found
> > bash-2.04$ 
> > 
> > I know the problem, switched to vi(m) ages ago tho :) It's a pity the -nw
> > switch doesn't do what it means - or rather, doesn't do it EXACTLY :)
> 
> How badly does it bleat if you, for instance,
>     ln -s /usr/lib/libc.so.? /usr/lib/libXaw.so.6
> (pick any library that exists?)
> 
>     David
>
I don't think that is a good solution. It is actually linked with much more
than 1 x library.  The correct solution is to have 2 binary packages in the
pkg tree, one that is linked against X and one that is not.  Basically the way
they did vim.

I may do this next weekend if I get the time.

Wayne