From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Mark Meyer <mark@ofosos.org>, 30266-done@debbugs.gnu.org
Subject: bug#30266: Add FANN
Date: Fri, 2 Feb 2018 23:12:07 +1000 [thread overview]
Message-ID: <c94dce13-59e1-901a-3b07-4a173bf563c4@uq.edu.au> (raw)
In-Reply-To: <1517499171.1017760.1256044528.7C0C62C3@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 3426 bytes --]
Thanks Mark. I made a few small changes and pushed the patch as
a9b34762391e6f3b066aef6fc1ebc614ec88db86.
On 02/02/18 01:32, Mark Meyer wrote:
> Thanks for the good feedback. Please consider the attached patch.
>
> Best, Mark
>
> On Sun, Jan 28, 2018, at 03:13, Ben Woodcroft wrote:
>>
>> Hi Mark,
>>
>> Thanks for the patch.
>>
>>> +(define-module (gnu packages ai)
>>> + #:use-module ((guix licenses) #:prefix license:)
>>> + #:use-module (guix utils)
>>> + #:use-module (guix download)
>>> + #:use-module (guix packages)
>>> + #:use-module (guix build-system cmake)
>>> + #:use-module (guix git-download)
>>> + #:use-module (gnu packages))
>> I think machine-learning.scm would be a good home for this package,
>> so a new file wouldn't be needed.
>>
>>
>>
>>> +
>>> +(define-public libfann
>>> + (package
>>> + (name "libfann")
>>> + (version "d71d54788b")
>>
>>
>> The last release is 129 commits behind and it has been some time, so
>> I think you are right - we should package from a git commit.
>>
>> Usually we package from git using this style though (i.e. reason for
>> not using the release, use of 'file-name', and a version that
>> includes the last release followed by '-1.<commit>').
>>
>> ;; There are no recent releases so we package from git.
>> (let ((commit "da121155a977197cab9fbb15953ca1b40b11eb87"))
>> (package
>> (name "newick-utils")
>> (version (string-append "1.6-1." (string-take commit 8)))
>> (source (origin
>> (method git-fetch)
>> (uri (git-reference
>> (url
>> "https://github.com/tjunier/newick_utils.git"
>> <https://github.com/tjunier/newick_utils.git>)
>> (commit commit)))
>> (file-name (string-append name "-" version "-checkout"))
>> (sha256
>> (base32
>> "1hkw21rq1mwf7xp0rmbb2gqc0i6p11108m69i7mr7xcjl268pxnb"))))
>>
>>
>>> + (source (origin
>>> + (method git-fetch)
>>> + (uri (git-reference
>>> + (url"https://github.com/libfann/fann.git"
>>> <https://github.com/libfann/fann.git>)
>>> + (commit version)))
>>> + (sha256
>>> + (base32
>>> + "0ibwpfrjs6q2lijs8slxjgzb2llcl6rk3v2ski4r6215g5jjhg3x"))))
>>> + (build-system cmake-build-system)
>>> + (arguments
>>> + `(#:tests? #f))
>> I see from the website:
>>
>>
>>
>>> Once you have installed the library you can test it out by going to
>>> the examples directory and type |make runtest|, which will compile
>>> the examples and run a few of them to test that everything is working.
>> Is that possible? Ideally, since there are tests it would be good to
>> run them.
>>
>>
>>> + (home-page"http://leenissen.dk/fann/wp/" <http://leenissen.dk/fann/wp/>)
>>> + (synopsis "Fast Artificial Neural Network")
>>> + (description
>>> + "FANN is a free open source neural network library, which implements
>>> +multilayer artificial neural networks in C with support for both fully
>>> +connected and sparsely connected networks.")
>>> + (license license:lgpl2.1)))
>> Otherwise LGTM. Can you send an updated patch please?
>>
>>
>> Thanks, ben
>>
>
> --
> Mark Meyer
> mark@ofosos.org
>
[-- Attachment #2: Type: text/html, Size: 5927 bytes --]
prev parent reply other threads:[~2018-02-02 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 12:55 [bug#30266] Add FANN Mark Meyer
2018-01-28 2:13 ` Ben Woodcroft
2018-02-01 15:32 ` Mark Meyer
2018-02-02 13:12 ` Ben Woodcroft [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
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=c94dce13-59e1-901a-3b07-4a173bf563c4@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=30266-done@debbugs.gnu.org \
--cc=mark@ofosos.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 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).