Firstly, thanks for the feedback!
On 09/03/2016, Leo Famulari <l...@famulari.name> wrote:
>> I therefore simply disabled it.
>
> I think that lots of software in our distribution has unused features or
> portability "goop" that doesn't apply to us, but we don't delete that
> code.
Running ‘./configure --disable-*’ isn't deleting code. The rest is a bugfix.
> So, it fails to build from source if you don't delete this file?
Correct.
> I still don't understand why we should delete the source file.
Because it fails to build from source if we don't.
Again, this is a stale (generated) file. Did you read the linked bug report?
There are various ways to code this, but none that don't amount to
deleting (generated) source files.[1]
> After searching online for "packagekit simple scan" I found the Nix
> package definition for Simple Scan 3.19.91. They
For the record: me.
> [...] 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")
But that alone is not enough. Not without removing the stale file.
Kind regards,
T G-R (nckx on #guix in about a quarter of an hour, if that helps :-)
[1] OK, ‘touch’ing random things, but that's just fooling make into
overwriting it, which is the same thing.
