<div dir="ltr">Hi<div><br></div><div>I have now pushed my changes that we discussed before. I have not started to join anything yet.<br></div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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:</div><div>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.</div><div>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...</div><div>3) Extension is installed, removed and re-installed with a no to the question. Shall it be disabled then?</div><div><br></div><div>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.</div><div><br></div><div>There is a reason why a something.d directory structure has been created for many packages.</div><div>Hmm it looks like we have that for xserver too. :-) I was not aware of that.</div><div><br></div><div>We can make a file in /usr/share/X11/xorg.conf.d/. That is probably the easiest.<br></div><div>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.</div><div><br></div><div>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. :-)</div><div><br></div><div>Cheers</div><div><br></div><div>// Ola</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 26, 2016 at 8:58 PM, Yaroslav Halchenko <span dir="ltr"><<a href="mailto:debian@onerussian.com" target="_blank">debian@onerussian.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
On Tue, 26 Jan 2016, Ola Lundqvist wrote:<br>
<br>
> Hi Yaroslav<br>
> I do not mind pushing the changes directly, but I thought you may want to<br>
> check things before as this was the first thing I did in this project.<br>
> Will push now.<br>
> I think both server packages can make use of the -common package.<br>
> Here I have a thought, why do we have separate server packages? I know the<br>
> FTP masters do not want unnecessary split of the packages. Is there any<br>
> specific reason why we have different pages for the scraping server, the<br>
> normal server and the library?<br>
> Just checking what your thoughts were regarding this.<br>
> Some facts:<br>
> - common ~60 KB<br>
> - scraping ~180 KB<br>
> - standalone ~1.1 MB<br>
> - xorg extension ~200 KB<br>
> The dependencies are quite similar too. The main difference is that the<br>
> extension do not need perl dependencies.<br>
> My suggestion is that we merge them together, but I do not want to do that<br>
> without your (common) approval :-)<br>
<br>
</span>I don't mind... unless someone sees some side-effect e.g. for xorg<br>
extension - may be for xorg extension we could eventually provide<br>
somehow configuration/debconf to enable it automagically when package<br>
gets installed? So I would vote to join scraping + standalone but may<br>
be leave xorg extension separately? if for extension we don't need<br>
anything of common -- we better suck common into the tightervnc-server<br>
package providing both scraping + standalone. So 2 pages instead of 4?<br>
<span class="im HOEnZb"><br>
--<br>
Yaroslav O. Halchenko<br>
Center for Open Neuroscience <a href="http://centerforopenneuroscience.org" rel="noreferrer" target="_blank">http://centerforopenneuroscience.org</a><br>
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755<br>
Phone: <a href="tel:%2B1%20%28603%29%20646-9834" value="+16036469834">+1 (603) 646-9834</a> Fax: <a href="tel:%2B1%20%28603%29%20646-1419" value="+16036461419">+1 (603) 646-1419</a><br>
WWW: <a href="http://www.linkedin.com/in/yarik" rel="noreferrer" target="_blank">http://www.linkedin.com/in/yarik</a><br>
<br>
</span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Pkg-tigervnc-devel mailing list<br>
<a href="mailto:Pkg-tigervnc-devel@lists.alioth.debian.org">Pkg-tigervnc-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><font face="courier new, monospace" size="1"> --------------------- Ola Lundqvist ---------------------------</font></div><div><font face="courier new, monospace" size="1">/ <a href="mailto:opal@debian.org" target="_blank">opal@debian.org</a> Annebergsslingan 37 \</font></div><div><font face="courier new, monospace" size="1">| <a href="mailto:ola@inguza.com" target="_blank">ola@inguza.com</a> 654 65 KARLSTAD |</font></div><div><font face="courier new, monospace" size="1">| <a href="http://inguza.com/" target="_blank">http://inguza.com/</a> +46 (0)70-332 1551 |</font></div><div><font face="courier new, monospace" size="1">\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /</font></div><div><font face="courier new, monospace" size="1"> ---------------------------------------------------------------</font></div><div><br></div></div></div>
</div>