From: rennes@openmailbox.org
To: guix-devel@gnu.org
Subject: [PATCH] gnu: Add spice-protocol.
Date: Thu, 11 Feb 2016 07:56:56 -0600 [thread overview]
Message-ID: <12541d95db51a675a0adc0d43464784e@openmailbox.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
Hi,
i attached spice-protocol patch for review.
SPICE protocol, is a required package to package spice-gtk(requiered for
GNOME Vinagre).
Considerations:
a) I use the source: "http://www.spice-space.org/download/releases/"
instead "https://cgit.freedesktop.org/spice/spice-protocol".
b) The home page "http://www.spice-space.org" instead
"https://cgit.freedesktop.org/spice/spice-protocol".
Thanks.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-Add-spice-protocol.patch --]
[-- Type: text/x-diff; name=0001-gnu-Add-spice-protocol.patch, Size: 2017 bytes --]
From 78ba6ffd6097e46b21d5ee9e8f1458a7768fae5d Mon Sep 17 00:00:00 2001
From: Rene Saavedra <rennes@openmailbox.org>
Date: Thu, 11 Feb 2016 07:31:06 -0600
Subject: [PATCH] gnu: Add spice-protocol.
* gnu/packages/gnome.scm (spice-protocol): New variable.
---
gnu/packages/gnome.scm | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index 49e6197..8b1caa6 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -4648,3 +4648,34 @@ as SASL, TLS and VeNCrypt. Additionally it supports encoding extensions.")
design and behaviour, giving the user a simple way to navigate and manage its
files.")
(license license:gpl2+)))
+
+(define-public spice-protocol
+ (package
+ (name "spice-protocol")
+ (version "0.12.10")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (string-append "http://www.spice-space.org/download/releases/"
+ name "-" version ".tar.bz2"))
+ (sha256
+ (base32
+ "1yrfacqgnabmx2q768mim892ga2wnlp5cavkf51v3idyjmqhv3vq"))))
+ (build-system glib-or-gtk-build-system)
+ (native-inputs
+ `(("python" ,python)))
+ (home-page "http://www.spice-space.org")
+ (synopsis "SPICE protocol module")
+ (description
+ "SPICE protocol defines a set of protocol messages for accessing,
+controlling, and receiving inputs from remote computing devices such as
+keyboard, video and mouse; across networks, and sending output to them.
+A controlled device can reside on either side, client and/or server.
+
+In addition, the protocol defines a set of calls for supporting migration
+of a remote server from one network address to another. Encryption of
+transported data, with one exception, was kept out of the protocol for
+maximum flexibility in choosing an encryption method. Spice uses simple
+messaging and does not depend on any RPC standard or a specific transport
+layer.")
+ (license license:gpl2+)))
--
2.6.3
next reply other threads:[~2016-02-11 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 13:56 rennes [this message]
2016-02-13 0:31 ` [PATCH] gnu: Add spice-protocol Leo Famulari
2016-02-13 2:55 ` rennes
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12541d95db51a675a0adc0d43464784e@openmailbox.org \
--to=rennes@openmailbox.org \
--cc=guix-devel@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).