[Pkg-tigervnc-devel] Request to Join Project TigerVNC package for Debian from Ola Lundqvist (opal)

[Ola Lundqvist]

Hi Yaroslav



On Mon, Jan 25, 2016 at 2:42 PM, Yaroslav Halchenko <debian at onerussian.com>
wrote:

>
> On Mon, 25 Jan 2016, Ola Lundqvist wrote:
>
> >      Thanks for joining in!!! Also yesterday, I thought... Gosh, we have
> to
> >      get TigerVNC ready for Debian stretch.
>
> >    Haha! I have been thinking that since wheezy or so ;-)
>
> Yeay -- welcome to the team the VNC master! ;)
>

Thanks. I'm honored. :-)


>
> Let me say -- "we have tried" (for wheezy or jessie, can't recall).  The
>

Very good to know. When you say so I do in fact recall that kind of
discussion some time (years) ago.


> primary problem was inclusion of xorg sources etc.  Since they we moved
>

The interesting this is that vnc4 and tightvnc are still allowed to be
there. They have exactly the same problem... :-/


> away from that and there is now xorg-server-source so we should all be
> kosher and indeed aim to reupload.  For that we need to finish updating
> it for 1.5.0 tigervnc or even jump over to recently released
> 1.6.0; and then re-review all the copyright etc
>
> But otherwise we indeed should be close to be ready ;)
>

Great. What do you want me to focus on?
- Review licenses?
- Update to latest versions? (I still struggle to build the current version
as I'm still running stable I guess)
- or something else?


> >      However, what I also thought yesterday for nx-X11 and TigerVNC
> alike:
> >      maybe we should drop the pkg-tigervnc-devel list and knock on the
> doors
> >      of the Debian X Strike Force and work under their umbrella. Thus,
> moving
> >      our interests more into the X Strike Force's team context.
>
> >    It is a possibility. However isn't it a risk that our discussions
> would be
> >    overwhelmed by the X activities? My guess is that the X.org
> activities are
> >    much more than this little package?
> >    What I have been thinking for many many years is to actually ask
> X.org to
> >    include the patches that we apply... That way we do not even have to
> >    maintain it at all :-)
> >    But maybe that is more for upstream to do. And of course there may be
> >    licensing issues that prevents that.
>
> yeah -- if we could join to offload tigervnc package upon them, it would
> be ok with me.  But joining rightfully to participate in all X
> activities, myself I would have no bandwidth and would need to drop off.
> So, IMHO, one step at a time -- finalize packaging, see patches being
> upstreamed, and then may be seek some merge of efforts.
>

Agree. Good plan.

// Ola

>
> Cheers,
> --
> 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 /
 ---------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-tigervnc-devel/attachments/20160125/8ceebc7a/attachment.html>