vnc module not requiring X

Richard Watson richard at doilywood.org.uk
Sun Jan 26 22:51:23 GMT 2003


Victor Pelt <peltco at mail.utexas.edu> writes:

> 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

Surely a dependency is a dependency? What measurement of obviousness
is used to decide what should and shouldn't be listed? What is gained
by not listing it?

And in any case there are vnc clients that do not require X, so it
doesn't even seem obvious to me that one would necessarily require
it. 

-- 
Richard Watson     
e-mail:richard at doilywood.org.uk  jabber:richard at jabber.doilywood.org.uk
http://www.opencolo.com/ - Value for money colocation


More information about the Lunar mailing list