[Pkg-tigervnc-devel] Request to Join Project TigerVNC package for Debian from Ola Lundqvist (opal)
Ola Lundqvist
opal at debian.org
Tue Jan 26 23:20:35 UTC 2016
Hi again
I have now been able to build the packages and could therefore also have a
look at the library dependencies. I found that they differ quite a lot, but
by investigating it more it is clear that the indirect dependencies are
very common, except the scraping server.
Summary:
1) The scraping server has two unique library dependencies: libxdamage1 (>=
1:1.1), libxtst6
2) The standalone server has one unique dependency: perl
3) The standalone and extension has quite a few dependencies that the
scraping server do not have.
4) It looks like the extension do not support jpeg compression (or do it
re-use something from xorg itself or compile it in statically?) nor TLS
encryption.
Do you know anything about that?
The scraping server clearly has less dependencies but that one should be
quite rarely used on a standalone server without X (just connecting to a
remote X server). It is certainly possible with such a setup but I do not
see how it is so important so it must be a separate package, unless we
should avoid the libxdamage1 and libxtst6 in the standalone and extension
of course.
The extension should really have a dependency on xserver-xorg. I mean it
really needs an Xserver to function. And in that case we should not have
that for the standalone and thus the extension should be separate... Soo,
maybe the separation is good as it is.
Here is a more detailed list. I have removed the ones that are common to
most packages in debian or that are common in this set.
Package: tigervnc-common
Depends: libgnutls-deb0-28 (>= 3.3.0), libice6 (>= 1:1.0.0),
libjpeg62-turbo (>= 1.3.1), libsm6, libx11-6 (>= 2:1.4.99.1), libxext6,
zlib1g (>= 1:1.1.4)
1) It looks like the vncconfig command is the one that do the reverse
connection. Not the server itself. This is quite interesting.
Package: tigervnc-scraping-server
Depends: libgnutls-deb0-28 (>= 3.3.0), libice6 (>= 1:1.0.0),
libjpeg62-turbo (>= 1.3.1), libsm6, libx11-6, *libxdamage1 (>= 1:1.1),*
libxext6,* libxtst6*, zlib1g (>= 1:1.1.4)
Unique depends: *libxdamage1 (>= 1:1.1),* *libxtst6*
Package: tigervnc-standalone-server
Depends: *libgcrypt20 (>= 1.6.1), libgl1-mesa-glx | libgl1*,
libgnutls-deb0-28 (>= 3.3.0), libjpeg62-turbo (>= 1.3.1),* libpixman-1-0
(>= 0.30.0), *libx11-6,* libxau6, libxdmcp6, libxfont1 (>= 1:1.4.2),
libxshmfence1,* zlib1g (>= 1:1.1.4), *perl*
Unique depends: perl
Package: tigervnc-xorg-extension
Depends: *libaudit1 (>= 1:2.2.1)*
1) No TLS support?
2) No jpeg support?
3) Inderect dependencies common with standalone server are:
libxau6, libgcrypt20, * libpixman-1-0, libxdmcp6, libxfont1,
**libxshmfence1,
libgl1-mesa-glx*
I think we should really add a dependency on xserver-xorg for this one. :-)
I'll do that unless some of you object.
// Ola
On Tue, Jan 26, 2016 at 9:29 PM, Ola Lundqvist <opal at debian.org> wrote:
> Hi
>
> I have now pushed my changes that we discussed before. I have not started
> to join anything yet.
>
> I think the vncconfig and vncpasswd commands are common for extension and
> standalone server so if we do not join the extension and the standalone we
> need to keep the common package separately.
>
> I do not think we should enable vnc automatically without a question on it
> first, since it is a policy violation to do so (edit some other
> configuration file). I see the RC bugs already now :-). This may be a
> security problem too. However when investigating it a little more I see
> that we can enable it automatically. See in the bottom of the mail.
>
> If we have a debconf question to enable it I do not see a problem to
> include it in the same package as the standalone anyway.
>
> However based on my experience on creating packages with debconf questions
> on enabling stuff I do not think it is worth the trouble. There are number
> of problematic scenarios that we have to consider namely:
> 1) Extension is first installed, someone edit the X config file to remove
> tigervnc and then the package is upgraded. It must not be enabled again
> then.
> 2) Extension is first installed, someone edit the X config file to remove
> tigervnc and then remove extension and install it again. Now it shall only
> be enabled if the question is asked...
> 3) Extension is installed, removed and re-installed with a no to the
> question. Shall it be disabled then?
>
> Well there are more problematic scenarios. I do not say it is impossible.
> I just say that this kind of automatic additions are quite cumbersome to
> make working.
>
> There is a reason why a something.d directory structure has been created
> for many packages.
> Hmm it looks like we have that for xserver too. :-) I was not aware of
> that.
>
> We can make a file in /usr/share/X11/xorg.conf.d/. That is probably the
> easiest.
> And this way it is still up to the admin to do the change (copy the files
> to /etc/xorg.conf.d). This way we should be able to merge also the extensio
> too.
>
> As you see I write a lot of should, meaning that I think this is how it
> would work, but I'm not sure and therefore I want you to think a little
> before accepting my statements. :-)
>
> Cheers
>
> // Ola
>
> On Tue, Jan 26, 2016 at 8:58 PM, Yaroslav Halchenko <debian at onerussian.com
> > wrote:
>
>>
>> On Tue, 26 Jan 2016, Ola Lundqvist wrote:
>>
>> > Hi Yaroslav
>> > I do not mind pushing the changes directly, but I thought you may
>> want to
>> > check things before as this was the first thing I did in this
>> project.
>> > Will push now.
>> > I think both server packages can make use of the -common package.
>> > Here I have a thought, why do we have separate server packages? I
>> know the
>> > FTP masters do not want unnecessary split of the packages. Is there
>> any
>> > specific reason why we have different pages for the scraping server,
>> the
>> > normal server and the library?
>> > Just checking what your thoughts were regarding this.
>> > Some facts:
>> > - common ~60 KB
>> > - scraping ~180 KB
>> > - standalone ~1.1 MB
>> > - xorg extension ~200 KB
>> > The dependencies are quite similar too. The main difference is that
>> the
>> > extension do not need perl dependencies.
>> > My suggestion is that we merge them together, but I do not want to
>> do that
>> > without your (common) approval :-)
>>
>> I don't mind... unless someone sees some side-effect e.g. for xorg
>> extension - may be for xorg extension we could eventually provide
>> somehow configuration/debconf to enable it automagically when package
>> gets installed? So I would vote to join scraping + standalone but may
>> be leave xorg extension separately? if for extension we don't need
>> anything of common -- we better suck common into the tightervnc-server
>> package providing both scraping + standalone. So 2 pages instead of 4?
>>
>> --
>> Yaroslav O. Halchenko
>> Center for Open Neuroscience http://centerforopenneuroscience.org
>> Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
>> Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
>> WWW: http://www.linkedin.com/in/yarik
>>
>> _______________________________________________
>> Pkg-tigervnc-devel mailing list
>> Pkg-tigervnc-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel
>>
>
>
>
> --
> --------------------- Ola Lundqvist ---------------------------
> / opal at debian.org Annebergsslingan 37 \
> | ola at inguza.com 654 65 KARLSTAD |
> | http://inguza.com/ +46 (0)70-332 1551 |
> \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
> ---------------------------------------------------------------
>
>
--
--------------------- Ola Lundqvist ---------------------------
/ opal at debian.org Annebergsslingan 37 \
| ola at inguza.com 654 65 KARLSTAD |
| http://inguza.com/ +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-tigervnc-devel/attachments/20160127/f530fe79/attachment.html>
More information about the Pkg-tigervnc-devel
mailing list