all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: kitzman <kitzman@disroot.org>
Cc: 54078@debbugs.gnu.org
Subject: [bug#54078] [PATCH] gnu: add libaml, libneatvnc, and wayvnc
Date: Wed, 23 Feb 2022 20:15:09 +0100	[thread overview]
Message-ID: <724ef26e516c2936acc17909385077ad41ff7a42.camel@telenet.be> (raw)
In-Reply-To: <87h78ppg0p.fsf_-_@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

kitzman schreef op wo 23-02-2022 om 20:57 [+0200]:
> Instead of copying the repo's description, now there are some
> functionalities of the library. However, it is unknown if they work
> with
> all clients. Do you think it's worth mentioning?

Different interpretations of the specifications and bugs causing
server-client incompatibilities, and clients not making use of all the
features offered by the server, is always possible.  As such, I don't
think documenting incompatibilities in the description of servers is
very meaningful (YMMV; I would accept a description mentioning
incompatibilities FWIW).

It might be interesting to document these features (or lack of
features) in the descriptions of the clients though.  E.g., encryption
can be very important, so if a client doesn't support that, that might
be good to mention in the description of the package of the client. 
SSH tunneling does not seem to be ‘core’ functionality of VNC but
rather an extra, so that also seems useful to document in the client.

(TBC, this is only superficial review, and I'm not a committer.)

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-02-23 19:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20 21:51 [bug#54078] [PATCH] gnu: add libaml, libneatvnc, and wayvnc kitzman via Guix-patches via
2022-02-21  8:06 ` [bug#54078] [PATCH 0/0] " kitzman via Guix-patches via
2022-02-21  8:09   ` [bug#54078] [PATCH 1/3] gnu: add libaml kitzman via Guix-patches via
2022-02-21 13:12     ` Maxime Devos
2022-02-23 17:50       ` kitzman via Guix-patches via
2022-02-23 17:58         ` Maxime Devos
2022-02-23 18:50           ` kitzman via Guix-patches via
2022-02-21  8:11   ` [bug#54078] [PATCH 2/3] gnu: add libneatvnc kitzman via Guix-patches via
2022-02-21 13:22     ` Maxime Devos
2022-02-23 18:57       ` [bug#54078] [PATCH] gnu: add libaml, libneatvnc, and wayvnc kitzman via Guix-patches via
2022-02-23 19:15         ` Maxime Devos [this message]
2022-02-23 21:02           ` kitzman via Guix-patches via
2022-02-21  8:12   ` [bug#54078] [PATCH 3/3] gnu: add wayvnc kitzman via Guix-patches via
2022-02-23 21:04     ` kitzman via Guix-patches via

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=724ef26e516c2936acc17909385077ad41ff7a42.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54078@debbugs.gnu.org \
    --cc=kitzman@disroot.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.