From: "Ludovic Courtès" <ludo@gnu.org>
To: L p R n d n <guix@lprndn.info>
Cc: 34189@debbugs.gnu.org
Subject: [bug#34189] [PATCH] gnu: Add arcan.
Date: Wed, 06 Feb 2019 22:32:49 +0100 [thread overview]
Message-ID: <8736p08uwu.fsf@gnu.org> (raw)
In-Reply-To: <cuca7jqrzba.fsf@lprndn.info> (L. p. R. n. d. n.'s message of "Thu, 24 Jan 2019 13:54:17 +0100")
Hello,
Sorry for the delay! Here are some comments.
L p R n d n <guix@lprndn.info> skribis:
>>From f1d5416c9d7a8a5ba5ecb4d380d06ee066b62a29 Mon Sep 17 00:00:00 2001
> From: Lprndn <guix@lprndn.info>
> Date: Thu, 24 Jan 2019 13:29:21 +0100
> Subject: [PATCH] gnu: Add arcan.
>
> * gnu/packages/arcan.scm New module.
> * gnu/packages/arcan.scm (arcan): New variable.
Should be just:
* gnu/packages/arcan.scm: New file.
> +++ b/gnu/packages/arcan.scm
> @@ -0,0 +1,130 @@
> +(define-module (gnu packages arcan)
Please add the standard GPLv3+ header with a copyright line for yourself.
> + (package
> + (name "arcan")
> + (version "0.5.5.2") ;A few commits ahead, really. To fix some bugs.
Please use the versioning scheme for Git snapshots explained here:
https://www.gnu.org/software/guix/manual/en/html_node/Version-Numbers.html
> + `("ARCAN_SCRIPTPATH" ":" suffix
> + (,(string-append out "/share/arcan/scripts")))))
[...]
> + (native-search-paths
> + (list (search-path-specification
> + (variable "ARCAN_APPLBASEPATH")
> + (separator #f)
> + (files '("share/arcan/appl")))))
Should ARCAN_SCRIPTPATH also be here?
> + ("arcan-openal" ,(origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/letoram/openal.git")
> + (commit "1c7302c580964fee9ee9e1d89ff56d24f934bdef")))
> + (sha256
> + (base32
> + "0dcxcnqjkyyqdr2yk84mprvkncy5g172kfs6vc4zrkklsbkr8yi2"))))))
Did you try vanilla OpenAL instead? If you have a pointer to a page
explaining why this variant is needed, that’d be great! Also please add
a ‘file-name’ for this ‘origin’.
> + (native-inputs
> + `(("pkg-config" ,pkg-config)
> + ("ruby" ,ruby))) ; For documentation and testing
> + (home-page "https://arcan-fe.com")
> + (synopsis "Combined display server, multimedia framework and game engine (egl-dri)")
Maybe just “Multimedia framework and game engine”?
> + (description "Arcan is a powerful development framework for creating virtually
> +anything from user interfaces for specialized embedded applications
> +all the way to full-blown desktop environments")
Missing period at the end, “powerful” is maybe not factual enough, and
it would be good if you could expound with just a sentence or two (see
<https://www.gnu.org/software/guix/manual/en/html_node/Synopses-and-Descriptions.html>).
> + (license (list license:gpl2+
> + license:lgpl2.0
> + license:bsd-3))))
Could you add a comment above explaining the meaning of the list
(whether it’s triple-licensed or what)?
Apart from that this LGTM. It’s great that you managed to unbundle
almost everything.
Could you send an updated patch?
Thanks!
Ludo’.
next prev parent reply other threads:[~2019-02-06 21:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 12:54 [bug#34189] [PATCH] gnu: Add arcan L p R n d n
[not found] ` <handler.34189.B.154833088612044.ack@debbugs.gnu.org>
2019-01-24 12:57 ` [bug#34189] Acknowledgement ([PATCH] gnu: Add arcan.) L p R n d n
2019-01-24 12:58 ` L p R n d n
2019-01-24 12:58 ` L p R n d n
2019-01-24 12:59 ` L p R n d n
2019-01-24 12:59 ` L p R n d n
2019-01-24 12:59 ` L p R n d n
2019-02-06 21:32 ` Ludovic Courtès [this message]
[not found] ` <cucwombb7y5.fsf@lprndn.info>
2019-02-09 21:42 ` [bug#34189] [PATCH] gnu: Add arcan Ludovic Courtès
2019-02-10 18:49 ` L p R n d n
2019-03-04 14:10 ` Ludovic Courtès
2021-07-13 13:15 ` bug#34189: " Maxim Cournoyer
2019-03-13 11:20 ` [bug#34189] " L p R n d n
2019-03-18 9:37 ` Ludovic Courtès
2019-03-18 11:02 ` L p R n d n
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=8736p08uwu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34189@debbugs.gnu.org \
--cc=guix@lprndn.info \
/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.