On Sat, Sep 24, 2016 at 03:27:45PM +, ng0 wrote:
> From 2fb504abdf78e63de0d538fd2cebef43b9fc38f6 Mon Sep 17 00:00:00 2001
> From: ng0
> Date: Wed, 21 Sep 2016 23:21:39 +
> Subject: [PATCH 1/2] gnu: Add python-lz4.
>
> * gnu/packages/compression.scm (python-lz4): New variable.
This bundle
Hi,
On Sat, 24 Sep 2016 19:16:23 +
ng0 wrote:
> Thanks for your tips.
> I tried to apply, but I might've gotten it wrong. Can you send this in
> patch form so I can be sure of what I change? Especially the linebreak
> is not good to understand just in ascii.
Sure. (It's a normal line break
Hi,
Danny Milosavljevic writes:
> On Sat, 24 Sep 2016 15:27:45 +
> ng0 wrote:
>> + (("^include_dirs.append")
> ^ remove "^"
>
> And add .*
>
> so
>
> ("include_dirs.append.*")
> ...
>
> Note that this also matches the newline codepoint (sigh), so you have
On Sat, 24 Sep 2016 15:27:45 +
ng0 wrote:
Note: Also add
#:test-target "check"
On Sat, 24 Sep 2016 15:27:45 +
ng0 wrote:
> + (("^include_dirs.append")
^ remove "^"
And add .*
so
("include_dirs.append.*")
...
Note that this also matches the newline codepoint (sigh), so you have to re-add
it in the substitution at the end.
("incl
On Sat, 24 Sep 2016 15:27:45 +
ng0 wrote:
> lz4: builds. lzo: I don't know how to make it find lzo headers, help
> requested.
python-lzo-1.11/setup.py hard-codes /usr/include/lzo . Substitute that by
(assoc-ref inputs "lzo") or something. Probably also set -Wl,-rpath there. When
testing, m
lz4: builds. lzo: I don't know how to make it find lzo headers, help
requested.
From 2fb504abdf78e63de0d538fd2cebef43b9fc38f6 Mon Sep 17 00:00:00 2001
From: ng0
Date: Wed, 21 Sep 2016 23:21:39 +
Subject: [PATCH 1/2] gnu: Add python-lz4.
* gnu/packages/compression.scm (python-lz4): New variab
