all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add python-lzo.
Date: Sun, 5 Feb 2017 11:37:40 +0000	[thread overview]
Message-ID: <20170205113740.wluulgh5yzrhauvm@wasp> (raw)
In-Reply-To: <87r33d7zmh.fsf@gmail.com>

On 17-02-05 01:31:18, Maxim Cournoyer wrote:
> Hi ng0,
> 
> contact.ng0@cryptolab.net writes:
> 
> > From: ng0 <ngillmann@runbox.com>
> >
> > * gnu/packages/compression.scm (python-lzo): New variable.
> >
> > Co-authored-by: Danny Milosavljevic <dannym@scratchpost.org>
> > ---
> >  gnu/packages/compression.scm | 36 ++++++++++++++++++++++++++++++++++++
> >  1 file changed, 36 insertions(+)
> >
> > diff --git a/gnu/packages/compression.scm b/gnu/packages/compression.scm
> > index 64518fb6b..2545c4517 100644
> > --- a/gnu/packages/compression.scm
> > +++ b/gnu/packages/compression.scm
> > @@ -365,6 +365,42 @@ LZO is written in ANSI C.  Both the source code and the compressed data
> >  format are designed to be portable across platforms.")
> >      (license license:gpl2+)))
> >  
> > +(define-public python-lzo
> > +  (package
> > +    (name "python-lzo")
> > +    (version "1.11")
> > +    (source
> > +     (origin
> > +       (method url-fetch)
> > +       (uri (pypi-uri "python-lzo" version))
> > +       (sha256
> > +        (base32
> > +         "11p3ifg14p086byhhin6azx5svlkg8dzw2b5abixik97xd6fm81q"))))
> > +    (build-system python-build-system)
> > +    (arguments
> > +     `(#:test-target "check"
> > +       #:phases
> > +       (modify-phases %standard-phases
> > +         (add-after 'unpack 'patch-setuppy
> > +           (lambda _
> > +             (substitute* "setup.py"
> > +               (("include_dirs.append.*")
> > +                (string-append "include_dirs.append(\""
> > +                               (assoc-ref %build-inputs "lzo") "/include/lzo" "\")
> > +"))))))))
> 
> A bit hard to read/long line here. Maybe the various string components
> being appended could be aligned below the string-append call? Also, you
> could use single quotes for the Python code which might help to
> differentiate what is what.

It is already applied. I think "it's hard to read" is more than just a
cosmetic fix, so if you have an idea how to make this more readable,
feel free to send a patch.

> Is the guix linter happy?
> 
> > +    (inputs
> > +     `(("lzo" ,lzo)))
> > +    (home-page "https://github.com/jd-boyd/python-lzo")
> > +    (synopsis "Python bindings for the LZO data compression library")
> > +    (description
> > +     "Python-LZO provides Python bindings for LZO, i.e. you can access
> > +the LZO library from your Python scripts thereby compressing ordinary
> > +Python strings.")
> > +    (license license:gpl2+)))
> > +
> > +(define-public python2-lzo
> > +  (package-with-python2 python-lzo))
> > +
> >  (define-public lzop
> >    (package
> >      (name "lzop")
> 
> Otherwise these 2 patches LGTM!
> 
> Maxim



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

      reply	other threads:[~2017-02-05 11:36 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
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 [this message]

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=20170205113740.wluulgh5yzrhauvm@wasp \
    --to=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@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.