all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Dennis Mungai <dmngaie@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Port Arrayfire to GNU Guix
Date: Mon, 04 Apr 2016 23:18:52 +0200	[thread overview]
Message-ID: <87a8l9ax8j.fsf@gnu.org> (raw)
In-Reply-To: <CAKKYfmHCYwgT-vt_komhAn=SJoU=hAc5w_naLMprOjja_ist=g@mail.gmail.com> (Dennis Mungai's message of "Sun, 20 Mar 2016 05:28:11 +0300")

Hi,

Dennis Mungai <dmngaie@gmail.com> skribis:

> The patch attached adds Arrayfire, a software library for GPU computing.
> For compliance with the GPL licenses, I've configured the package not
> to build with CUDA support, and the OpenCL backend builds with the
> open source OpenCL ICD and the standard Khronos OpenCL headers for
> vendor neutrality.

Sorry for the late reply, and thanks for your work!

> From c25732b9beb99a0788349c086f460d45f228dd74 Mon Sep 17 00:00:00 2001
> From: Dennis Mungai <dmngaie@gmail.com>
> Date: Sun, 20 Mar 2016 04:51:15 +0300
> Subject: [PATCH] Ported ArrayFire to GNU Guix
>
> ---
>  arrayfire.scm | 362 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Could you:

  1. Send a patch against Guix ‘master’, where this file should be
     called gnu/packages/opencl.scm?  (I think ‘opencl’ is more
     appropriate than ‘arrayfire’.)

  2. Send one patch per package, to simply the review workflow?

  3. Run ‘guix lint’ for each package and address any problems it raises
     (hopefully simple to do, but feel free to ask for help on #guix).

  4. Provide ChangeLog-style commit logs, as noted at
     <https://www.gnu.org/software/guix/manual/html_node/Submitting-Patches.html>?

That’s a bit of extra work, but it will really help us!

Some more specific comments:

> +(define-module (gn packages arrayfire)

s/gn/gnu/

> +(define-public arrayfire
> +(package
> +    (name "arrayfire")

Please try to indent as in the other files.

> +       ("cmake" ,cmake)))
> +    (build-system cmake-build-system)

CMake is not needed in ‘inputs’ when using ‘cmake-build-system’.

> +    (arguments 
> +     `(#:configure-flags '("-DBUILD_OPENCL=ON" "-DBUILD_CUDA=OFF" "-DBUILD_GRAPHICS=OFF" "-DUSE_SYSTEM_BOOST_COMPUTE=ON" "-DUSE_SYSTEM_CLBLAS=ON" "-DUSE_SYSTEM_CLFFT=ON") 
> +       #:tests? #f))     

Please add a comment above #:tests? #f to justify why tests are skipped.

> +    (synopsis "ArrayFire: a general purpose GPU library. https://arrayfire.com")
> +    (description "ArrayFire is a high performance software library for parallel computing with an easy-to-use API. Its array based function set makes parallel programming simple.Now on Guix")

‘guix lint’ will suggest some changes here.  :-)

> +    (home-page "http://arrayfire.com/")
> +    (license (list license:gpl2 
> +                   license:gpl2+ 
> +                   license:gpl3 
> +                   license:gpl3+))))

What does it mean?  Please add a comment above explaining what the
license list is about.

> +    (synopsis "glfw is an Open Source, multi-platform library for creating windows with OpenGL contexts and receiving input and events.")
> +    (description "glfw is an Open Source, multi-platform library for creating windows with OpenGL contexts and receiving input and events.")

s/Open Source//g

The GNU project focuses on free software, not “open source” (see
<https://www.gnu.org/philosophy/open-source-misses-the-point.html>), and
since every package in Guix is free, we don’t mention it in synopses.

Also, please see
<https://www.gnu.org/software/guix/manual/html_node/Synopses-and-Descriptions.html>
on the kind of synopses/descriptions we try to provide to our users.

> +(define-public clBLAS
> +  (package
> +    (name "clBLAS")

Variable and package names should be lower-case.

> +    (version "v2.10")

No “v”.

> +    (native-inputs `(("autoconf" ,autoconf)
> +        ("automake" ,automake)

Indentation.

> +(define-public opencl-headers
> +(let ((commit "c1770dc"))
> +  (package

Indentation.

Could you send updated patches, preferably using ‘git send-email’?

Thank you!

Ludo’.

      reply	other threads:[~2016-04-04 21:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-20  2:28 [PATCH] Port Arrayfire to GNU Guix Dennis Mungai
2016-04-04 21:18 ` Ludovic Courtès [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=87a8l9ax8j.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dmngaie@gmail.com \
    --cc=guix-devel@gnu.org \
    /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.