unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "ng0" <contact.ng0@cryptolab.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: "guix-devel@gnu.org >> guix-devel" <guix-devel@gnu.org>
Subject: Re: [PATCH 2/2] gnu: Add python-lzo.
Date: Fri, 03 Feb 2017 13:13:20 +0000	[thread overview]
Message-ID: <87fujvh0y7.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <58939758.9020507@crazy-compilers.com>


Hartmut Goebel writes:

> Am 02.02.2017 um 16:16 schrieb contact.ng0@cryptolab.net:
>> +                (string-append "include_dirs.append(\""
>> +                               (assoc-ref %build-inputs "lzo") "/include/lzo" "\")
>
> You could use single quotes for teh python string to make it more readable:

I think there was a reason for the way it was written. Your
suggestion below makes the substitute fail with:

ERROR: In procedure primitive-load-path:
ERROR: In procedure scm_lreadr: gnu/packages/compression.scm:387:44: illegal character in escape sequence: #\)

>
> string-append "include_dirs.append('" + (assoc-ref %build-inputs "lzo")
> "/include/lzo" "')
>
>
>> +"))))))))
>
> Also this line-break is confusing. I suggest either using "\n" or to
> change the substitute into something like:
>
>
> +             (substitute* "setup.py"
> +               (("include_dirs.append\(.*\)")  ;; match up to the trailing parent only, not the new-line
> +                (string-append "include_dirs.append('"
> +                               (assoc-ref %build-inputs "lzo") "/include/lzo"
> +                               "')"))))))))   ;; put these last few characters on the next line
>
> Otherwise LGTM.


-- 
ng0 . https://www.inventati.org/patternsinthechaos/

  reply	other threads:[~2017-02-03 13:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 15:16 LZ4 + LZO python bindings contact.ng0
2017-02-02 15:16 ` [PATCH 1/2] gnu: Add python-lz4 contact.ng0
2017-02-02 20:32   ` Hartmut Goebel
2017-02-02 15:16 ` [PATCH 2/2] gnu: Add python-lzo contact.ng0
2017-02-02 20:32   ` Hartmut Goebel
2017-02-03 13:13     ` ng0 [this message]
2017-02-03 15:56       ` Hartmut Goebel
2017-02-03 16:36         ` ng0
2017-02-04 13:42           ` substitute/regex (was [PATCH 2/2] gnu: Add python-lzo.) Hartmut Goebel
2017-02-03 16:56         ` python-{lzo,lz4} ,v3 contact.ng0
2017-02-03 16:56           ` [PATCH 1/2] gnu: Add python-lz4 contact.ng0
2017-02-03 16:56           ` [PATCH 2/2] gnu: Add python-lzo contact.ng0
2017-02-04 13:46           ` python-{lzo,lz4} ,v3 Hartmut Goebel
2017-02-05  9:31   ` [PATCH 2/2] gnu: Add python-lzo Maxim Cournoyer
2017-02-05 11:37     ` ng0

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=87fujvh0y7.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
    --to=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.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).