vnc module not requiring X

[Rick Altherr]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

glibc, gcc, and linux are assumed.  That is because every module in the 
moonbase requires them.  As for X, the debate has been going on for a while.  
It's pretty much boiled down to, if someone adds X as a dependency to the 
toolkits and other things that require X (i.e. programs that doen't require X 
via another dependency) then it will stay that way, but until then, nothing 
requires X.

Rick
On Sunday 26 January 2003 06:05 pm, Victor Pelt wrote:
> my understanding?
> x, glibc, linux (kernel) and windows managers are all left out
>
> but maybe one of the lunar developers could further explain this
>
> On Sun, 2003-01-26 at 16:51, Richard Watson wrote:
> > 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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+NHGxfHskbXA7ozgRAniEAJ9MtEBkokKKKCfktDh5YpI1HNsgVwCePnBu
w7O/YCPovk25Ae4bUJbZtNY=
=rHW2
-----END PGP SIGNATURE-----