From: Christine Lemmer-Webber <cwebber@dustycloud.org>
To: Christopher Rodriguez <yewscion@gmail.com>
Cc: 54529@debbugs.gnu.org
Subject: [bug#54529] [PATCH v3] Added orca-lang package
Date: Fri, 25 Mar 2022 17:55:12 -0400 [thread overview]
Message-ID: <87zgldwvaw.fsf@dustycloud.org> (raw)
In-Reply-To: <20220323144547.23041-1-yewscion@gmail.com>
First: this is awesome. Second...
Christopher Rodriguez <yewscion@gmail.com> writes:
> Here's the patch. Let me know what else can be improved.
>
> Particularly, I am worried about the name of the binary. It is
> currently installed as `orca`, which is (I believe) the same name
> given to the binary for the orca screen reader.
>
> Should I change this? And if so, how?
I think you could probably just add a post-install phase that moves the
binary file in its output directory from "orca" to "orca-music"?
Why not give it a try anyway? :)
> gnu/packages/music.scm | 57 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 57 insertions(+)
>
> diff --git a/gnu/packages/music.scm b/gnu/packages/music.scm
> index 9c8203aa80..1240027050 100644
> --- a/gnu/packages/music.scm
> +++ b/gnu/packages/music.scm
> @@ -6879,3 +6879,60 @@ (define-public musikcube
> streaming audio server.")
> (home-page "https://musikcube.com/")
> (license license:bsd-3)))
> +(define-public orca-music
> + (let ((commit "5ba56ca67baae3db140f8b7a2b2fc46bbac5602f") (revision "1"))
> + (package
> + (name "orca-music")
> + ;; No upstream version numbers; Using commit instead.
> + (version (git-version "0" revision commit))
> + (source (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://git.sr.ht/~rabbits/orca")
> + (commit commit)))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32
> + "1mnhk68slc6g5y5348vj86pmnz90a385jxvm3463fic79k90gckd"))))
> + (build-system gnu-build-system)
> + (arguments
> + `(#:phases (modify-phases %standard-phases
> + (delete 'configure) ;; No autoconf
> + (delete 'check) ;; No make check
> + (replace 'build
> + (lambda* (#:key inputs outputs #:allow-other-keys)
> + (setenv "CC"
> + ,(cc-for-target))
> + (invoke "make" "release")))
> + (replace 'install
> + (lambda* (#:key outputs #:allow-other-keys)
> + (let* ((out (assoc-ref outputs "out")) (dest-bin (string-append
> + out
> + "/bin"))
> + (share (string-append out "/share"))
> + (dest-examples (string-append share "/examples"))
> + (dest-doc (string-append share "/doc")))
> + (install-file "./build/orca" dest-bin)
> + (copy-recursively "./examples" dest-examples)
> + (install-file "./README.md" dest-doc)))))))
> + (inputs (list ncurses portmidi))
> + (native-inputs (list pkg-config))
> + ;; The below are needed as propagated inputs to let orca interact with
> + ;; alsa/pulse MIDI.
> + (propagated-inputs `(("alsa-plugins" ,alsa-plugins) ("alsa-plugins:pulseaudio" ,alsa-plugins
> + "pulseaudio")))
> + (native-search-paths (list
> + (search-path-specification
> + (variable "TERMINFO_DIRS")
> + (files '("share/terminfo")))))
> + (synopsis "musical live-coding environment")
> + (description
> + "This is the C implementation of the ORCΛ language and terminal
> +livecoding environment. It's designed to be power efficient. It can handle
> +large files, even if your terminal is small.
> +
> +Orca is not a synthesizer, but a flexible livecoding environment capable of
> +sending MIDI, OSC, and UDP to your audio/visual interfaces like Ableton,
> +Renoise, VCV Rack, or SuperCollider.")
> + (home-page "https://100r.co/site/orca.html")
> + (license license:expat))))
next prev parent reply other threads:[~2022-03-25 21:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 22:46 [bug#54529] [PATCH] Added orca-lang package Christopher Rodriguez
2022-03-23 2:30 ` [bug#54529] [PATCH v2] " Christopher Rodriguez
2022-03-23 7:29 ` Maxime Devos
2022-03-23 7:29 ` Maxime Devos
2022-03-23 7:30 ` Maxime Devos
2022-03-23 7:30 ` Maxime Devos
2022-03-23 7:30 ` Maxime Devos
2022-03-23 7:32 ` Maxime Devos
2022-03-23 7:33 ` Maxime Devos
2022-03-23 7:33 ` Maxime Devos
2022-03-23 7:34 ` Maxime Devos
2022-03-23 7:35 ` Maxime Devos
2022-03-23 7:36 ` Maxime Devos
2022-03-23 7:36 ` Maxime Devos
2022-03-23 7:36 ` Maxime Devos
2022-03-23 7:38 ` Maxime Devos
2022-03-23 7:38 ` Maxime Devos
2022-03-23 7:40 ` Maxime Devos
2022-03-23 14:45 ` [bug#54529] [PATCH v3] " Christopher Rodriguez
2022-03-25 21:55 ` Christine Lemmer-Webber [this message]
2022-03-29 18:51 ` [bug#54529] [PATCH v4] " Christopher Rodriguez
2022-04-18 15:07 ` [bug#54529] Checking In Christopher Rodriguez
2022-04-21 15:59 ` Christine Lemmer-Webber
2022-04-22 1:20 ` Christopher Rodriguez
2022-06-11 17:55 ` Christine Lemmer-Webber
2022-06-12 18:35 ` Christopher Rodriguez
2022-06-13 2:38 ` Christine Lemmer-Webber
2022-06-13 2:48 ` [bug#54529] [PATCH v5] Added orca-music package Christopher Rodriguez
2022-06-26 19:43 ` Christine Lemmer-Webber
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=87zgldwvaw.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=54529@debbugs.gnu.org \
--cc=yewscion@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 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).