Re: [Libvncserver-common] Bug#845106: #845106: x11vnc: configure does not find libssl, builds without OpenSSL support

[Christian B. <chr...@go...>]

Am Mon, 19 Dec 2016 08:11:45 +0100
schrieb Christian Hofstaedtler <ze...@de...>:

> Control: reopen -1
> Control: severity -1 important
> 
> For stretch this is worked around by using libssl1.0, for stretch+1
> this needs a proper fix. By then, we hopefully don't need to
> traverse 5000 lines of openssl glue.
> 

Hi all,

Note that we have an x11vnc reportedly working with OpenSSL 1.1.0 over at LibVNC
since a few days [1]. I might do a new release soonish, but I'm unsure whether
or not we can consider this x11vnc "the real one" or a more sort of a fork.
Here's the facts:

* https://github.com/LibVNC/x11vnc is the original x11vnc source tree (plus
  some additions during the last years) that used to live within the
  LibVNCServer tree but was split out by me in the course of LibVNCServer's
  sf->github migration.
* Besides adding in XInput2 multi-pointer support, the codebase has largely
  been in maintenance mode.
* I wrote to Karl, the original author, back in 2014 [2], asking him about
  splitting out x11vnc from the LibVNCServer repo (which I manage) but as of now
  did not get a reply.
* There haven't been any commits from Karl to the LibVNCServer
  repo since early 2011, nor any changes to his -dev tarball  [3] since a few
  years.

So, honestly, I don't know what should happen when the original author of some
project apparently goes MIA. (Are you there, Karl?) Can the community simply
"take over" the project or should https://github.com/LibVNC/x11vnc technically
considered to be a fork?

What is Debian's experience with situations like that? I'm sure stuff like this
has happened before...

Cheers,
   Christian


[1] https://github.com/LibVNC/x11vnc/commit/d37dac6963c2fb65cf577a6413657621cbcb406a
[2] https://sourceforge.net/p/libvncserver/mailman/message/32196002/
[3] http://www.karlrunge.com/x11vnc/#beta-test