[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

VNC plans.


Some people might have notived that I have made some
(dramatic?) changes to the vnc packages. The reason is
that the upstream development have started again. :)

The problem is that I used to have the tightvnc patches
applied but due to the upstreams is so different, that is
not possible anymore. The new upstream has nice new features
and tightvnc has other nice features. They may coexist in
the future but that is far away.

So this is what I intend to do to solve these issues:

0) Start using alternatives for vnc.

0.1) Link svncviewer staically with libvncauth instead
   of dynamically.

1) Package tightvnc as:
   tightvncserver, provides vncserver
   tight[x?]vncclient, provides vncviewer

   The hard part is to test that they can coexist.

2) Change the vnc package to realvnc
   realvncserver, provides vncserver
   realvncviewer, provides vncviewer
   vnc-common (I have to check what's in there).

3) Ask for the removal of the old vnc packages.

4) Change name of vnc-java to realvnc-java

5) Package tightvnc-java.

So now I have some questions.

1) Do you think this is an ok plan?
2) Do I have to ask for vncserver and vncviewer as they
   become virtual packages?


// Ola

PS. Now I have to get some food. Will be back tomorrow. :)

 --------------------- Ola Lundqvist ---------------------------
/  opal@debian.org                     Annebergsslingan 37      \
|  opal@lysator.liu.se                 654 65 KARLSTAD          |
|  +46 (0)54-10 14 30                  +46 (0)70-332 1551       |
|  http://www.opal.dhs.org             UIN/icq: 4912500         |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /

Reply to: