all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Leo Famulari <leo@famulari.name>
Cc: 39228@debbugs.gnu.org
Subject: [bug#39228] [PATCH] gnu: Add libvnc.
Date: Wed, 22 Jan 2020 09:47:58 +0100	[thread overview]
Message-ID: <e3f07a1e-fe31-92f9-9e5e-042aeea679df@crazy-compilers.com> (raw)
In-Reply-To: <20200121215759.GB9078@jasmine.lan>


[-- Attachment #1.1: Type: text/plain, Size: 670 bytes --]

Am 21.01.20 um 22:57 schrieb Leo Famulari:
> I notice we have a package module 'gnu/packages/tigervnc.scm'. Maybe we
> can combine that module with this one as 'gnu/packages/vnc.scm'?

I thought about this, too, but hesitated. The module `tighervnc` seems
to not be used anywhere, thus renaming it would be easy.

If this is okay, I would go forward and:

1. renaming `tigervnc.scm` into `vnc.scm` (as proposed by you)

2. add libvnc to this module.

3. push to master.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-01-22  8:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 21:10 [bug#39228] [PATCH] gnu: Add libvnc Hartmut Goebel
2020-01-21 21:52 ` [bug#39228] [Patch v2] " Hartmut Goebel
2020-01-21 21:57 ` [bug#39228] [PATCH] " Leo Famulari
2020-01-22  8:47   ` Hartmut Goebel [this message]
2020-01-22  9:16     ` Efraim Flashner
2020-01-22 12:09       ` bug#39228: " Hartmut Goebel
2020-01-22 12:17         ` [bug#39228] " Jonathan Brielmaier
2020-01-22 12:21           ` Hartmut Goebel
2020-01-22 17:33             ` Leo Famulari
2020-01-22 17:43               ` Jonathan Brielmaier

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=e3f07a1e-fe31-92f9-9e5e-042aeea679df@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=39228@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.