From: Leo Famulari <leo@famulari.name>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org, rennes@openmailbox.org, 宋文武 <iyzsong@gmail.com>
Subject: Re: [PATCH 2/2] gnu: Add gnome-tweak-tool.
Date: Sun, 17 Apr 2016 14:44:28 -0400 [thread overview]
Message-ID: <20160417184428.GA21041@jasmine> (raw)
In-Reply-To: <87vb3gp2uk.fsf@drakenvlieg.flower>
On Sun, Apr 17, 2016 at 07:22:27PM +0200, Jan Nieuwenhuizen wrote:
> Leo Famulari writes:
>
> > I tried building with glib-or-gtk-build-system instead of
> > gnu-build-system. It still didn't work if python-2 was a mere input, but
> > I wonder if glib-or-gtk-build-system should be used, regardless?
>
> The glib-or-gtk-build-system lists in two additions to the
> gnu-build-system. I don't see gnome-tweak-tool needing any of those,
> do you?
>
> Gnome-tweak-tool is written in python2: it won't run without it. How
> could loosening the python2 dependency be helpful?
Ah, I didn't realize it was a Python program with an Autotools build
system.
I think we need to wrap gnome-tweak-tool's executable, which the
python-build-system normally does automatically. AIUI, that's why all of
the python-build-system packages don't require Python itself to be
propagated.
next prev parent reply other threads:[~2016-04-17 18:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 11:07 [PATCH 2/2] gnu: Add gnome-tweak-tool Jan Nieuwenhuizen
2016-04-03 16:41 ` Jan Nieuwenhuizen
2016-04-11 23:35 ` Leo Famulari
2016-04-13 18:02 ` Jan Nieuwenhuizen
2016-04-16 1:35 ` Leo Famulari
2016-04-17 17:22 ` Jan Nieuwenhuizen
2016-04-17 18:33 ` rennes
2016-04-17 18:44 ` Leo Famulari [this message]
2016-04-24 11:19 ` Jan Nieuwenhuizen
2016-04-24 18:50 ` Leo Famulari
2016-04-27 19:05 ` Jan Nieuwenhuizen
2016-05-01 21:36 ` rennes
2016-05-02 22:04 ` Leo Famulari
2016-05-02 22:38 ` Jan Nieuwenhuizen
2016-05-03 2:19 ` Leo Famulari
2016-05-15 17:31 ` Leo Famulari
[not found] <mailman.877.1460442807.7476.guix-devel@gnu.org>
2016-04-12 13:16 ` 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=20160417184428.GA21041@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=iyzsong@gmail.com \
--cc=janneke@gnu.org \
--cc=rennes@openmailbox.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).