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: Wed, 9 Mar 2016 02:49:14 -0500 [thread overview]
Message-ID: <20160309074914.GA18130@jasmine> (raw)
In-Reply-To: <20160309013937.GA25866@jasmine>
On Tue, Mar 08, 2016 at 08:39:37PM -0500, Leo Famulari wrote:
> On Wed, Mar 09, 2016 at 01:25:04AM +0100, Tobias Geerinckx-Rice wrote:
> > On 09/03/2016, Leo Famulari <leo@famulari.name> wrote:
> > > [...] pass to ./configure '--disable-packagekit'. Would that work?
> >
> > So do ‘we’:
> >
> > On Tue, Mar 08, 2016 at 11:04:35PM +0100, Tobias Geerinckx-Rice wrote:
> > > '(#:configure-flags '("--disable-packagekit")
>
> Oops! Serves me right for trying to squeeze this review in earlier ;)
>
> > There are various ways to code this, but none that don't amount to
> > deleting (generated) source files.[1]
>
> I didn't realize this was generated C code. In that case it's closer to
> a compiled binary than source code, don't you think? Can we delete all
> the generated files and rebuild them from source?
Anyways, that is probably something to look into later. I think it makes
sense to do this update, remove that file, and include a link to the bug
report with a bit of context.
Does anyone have any objections to that plan?
next prev parent reply other threads:[~2016-03-09 7:49 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
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 [this message]
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
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=20160309074914.GA18130@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 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).