From: Leo Famulari <leo@famulari.name>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 03/04] gnu: Add python2-xdo
Date: Sat, 6 Feb 2016 03:40:35 -0500 [thread overview]
Message-ID: <20160206084035.GE1432@jasmine> (raw)
In-Reply-To: <87bn7ufqhg.fsf@dustycloud.org>
On Fri, Feb 05, 2016 at 07:48:59PM -0800, Christopher Allan Webber wrote:
> * gnu/packages/python.scm (python2-xdo): New variable.
[...]
> + (source (origin
> + (method url-fetch)
> + (uri (string-append
> + "http://http.debian.net/debian/pool/main/p/python-xdo/python-xdo_"
If this line is longer than 80 characters, please split the string onto
the next line.
> + version ".orig.tar.gz"))
> + (sha256
> + (base32
> + "1kl5c1p0dyxf62plnk6fl77ycfb4whwjms16r14dxx8kn90hlqz4"))))
> + (build-system python-build-system)
> + (arguments
> + `(#:python ,python-2
> + #:tests? #f)) ; no tests provided
> + (inputs
> + `(("xdotool" ,xdotool)
> + ("libX11" ,libx11)))
> + (home-page "https://tracker.debian.org/pkg/python-xdo")
Is it developed within Debian? Interesting if so!
> + (synopsis "Python library for simulating X11 keyboard/mouse input (libxdo bindings)")
Line length? The linter should complain if the synopsis is too long.
> + ;; Note about this being a legacy
Did you mean to leave this comment in? ;)
> + (description "Provides bindings to libxdo for manipulating X11 via simulated
> +input. (Note that this is mostly a legacy library; you may wish to look at
> +python-xdo for newer bindings.)")
I see, so this is a python-2 specific legacy package?
> + (license bsd-3)))
> +
> --
> 2.6.3
>
>
next prev parent reply other threads:[~2016-02-06 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 3:48 [PATCH 03/04] gnu: Add python2-xdo Christopher Allan Webber
2016-02-06 8:40 ` Leo Famulari [this message]
2016-02-06 22:59 ` Christopher Allan Webber
2016-02-07 21:12 ` Leo Famulari
2016-02-07 22:59 ` Christopher Allan Webber
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=20160206084035.GE1432@jasmine \
--to=leo@famulari.name \
--cc=cwebber@dustycloud.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 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.