vnc module not requiring X

[Victor Pelt]

i think it was decided that X was an "obvious" dependency and therefore
wouldn't be listen as dependency for modules

the same applies for windowsmanagers etc

On Sun, 2003-01-26 at 14:55, Todd A. Jacobs wrote:
> The vnc module claims to have no dependencies. Of course, it fails if you 
> try to install it without X:
> 
> vncconnect.c:29:23: X11/Xatom.h: No such file or directory
> vncconnect.c:31: syntax error before "static"
> vncconnect.c: In function `main':
> vncconnect.c:51: `Atom' undeclared (first use in this function)
> vncconnect.c:51: (Each undeclared identifier is reported only once
> vncconnect.c:51: for each function it appears in.)
> vncconnect.c:51: parse error before "prop"
> vncconnect.c:86: `prop' undeclared (first use in this function)
> vncconnect.c:88: parse error before "dpy"
> vncconnect.c:88: parse error before "dpy"
> vncconnect.c:88: `XA_STRING' undeclared (first use in this function)
> vncconnect.c:89: `PropModeReplace' undeclared (first use in this function)
> make[1]: *** [vncconnect.o] Error 1
> make[1]: Leaving directory `/usr/src/vnc-3.3.5-unixsrc/vncconnect'
> make: *** [all] Error 1
>  ! Problem Detected ! 
-- 
Victor Pelt <peltco at mail.utexas.edu>