From: Leo Famulari <leo@famulari.name>
To: Tobias Geerinckx-Rice <tobias.geerinckx.rice@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: simple-scan: Update to 3.19.91.
Date: Tue, 8 Mar 2016 18:02:32 -0500 [thread overview]
Message-ID: <20160308230232.GA24107@jasmine> (raw)
In-Reply-To: <1457474675-21775-1-git-send-email-tobias.geerinckx.rice@gmail.com>
On Tue, Mar 08, 2016 at 11:04:35PM +0100, Tobias Geerinckx-Rice wrote:
> * gnu/packages/gnome.scm (simple-scan): Update to 3.19.91.
Thanks for your attention to this package!
Except where necessary for the new version to work, it's best to do
updates in a separate commit from other changes.
I can apply the update myself if you say it's okay to do on its own, or
feel free to submit a revised patch set.
> [arguments]: Disable PackageKit support irrelevant for Guix.
[...]
> + (arguments
> + '(#:configure-flags '("--disable-packagekit")
> + #:phases
> + (modify-phases %standard-phases
> + (add-after 'unpack 'clean
> + (lambda _
> + ;; Remove a left-over reference to PackageKit.
> + (delete-file "src/ui.c"))))))
Does 'src/ui.c' cause problems for us? I'd rather not make changes to
upstream code except when necesssary [0], at least not without
discussing it with upstream first.
[0] For example, when fixing portability issues or deleting non-free and
non-essential bundled components. The impact of the change should be
well-understood by reviewers, at the very least ;)
next prev parent reply other threads:[~2016-03-08 23:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 22:04 [PATCH] gnu: simple-scan: Update to 3.19.91 Tobias Geerinckx-Rice
2016-03-08 23:02 ` Leo Famulari [this message]
2016-03-08 23:43 ` Tobias Geerinckx-Rice
2016-03-08 23:50 ` Tobias Geerinckx-Rice
2016-03-09 0:05 ` Leo Famulari
2016-03-09 0:25 ` Tobias Geerinckx-Rice
2016-03-09 1:39 ` Leo Famulari
2016-03-09 7:49 ` Leo Famulari
2016-03-09 13:28 ` Ludovic Courtès
2016-03-09 20:56 ` Leo Famulari
2016-03-12 20:33 ` Danny Milosavljevic
2016-03-13 10:34 ` Danny Milosavljevic
2016-03-13 16:27 ` Tobias Geerinckx-Rice
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=20160308230232.GA24107@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=tobias.geerinckx.rice@gmail.com \
/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.