unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: jgart <jgart@dismail.de>
Cc: 62393@debbugs.gnu.org
Subject: [bug#62393] [PATCH 1/2] gnu: Add cl-collider.
Date: Mon, 27 Mar 2023 09:07:50 +0000	[thread overview]
Message-ID: <87leji366i.fsf@kitej> (raw)
In-Reply-To: <5a7282791b5c076e6c51466198aec4ac@dismail.de>

[-- Attachment #1: Type: text/plain, Size: 724 bytes --]

Patch for cl-osc pushed as acbdaec070f39b723a1b964ffa7fbd4b640bbd8e.

Concerning the patch for cl-collider, the 'patch-executables' phase
replaces "jack-connect" with "scsynth":

--8<---------------cut here---------------start------------->8---
(add-after 'unpack 'patch-executables
  (lambda* (#:key inputs #:allow-other-keys)
    (substitute* "server.lisp"
      (("which scsynth")
       (search-input-file inputs "/bin/scsynth"))
      (("jack_connect")
       (search-input-file inputs "/bin/scsynth")))))
--8<---------------cut here---------------end--------------->8---

Is it really supposed to be like that?

Also, in "server.lisp", doesn't the path for plugins (*sc-plugin-paths*
variable) need to be patched too?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2023-03-27  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 21:34 [bug#62393] [PATCH 1/2] gnu: Add cl-collider jgart via Guix-patches via
2023-03-22 21:57 ` [bug#62393] [PATCH 1/2] gnu: Add cl-osc jgart via Guix-patches via
2023-03-22 21:57   ` [bug#62393] [PATCH 2/2] gnu: Add cl-collider jgart via Guix-patches via
2023-03-27  9:07 ` Guillaume Le Vaillant [this message]
2023-03-28  4:23 ` [bug#62393] [PATCH v2] " jgart via Guix-patches via
2023-03-29  1:31 ` [bug#62393] [PATCH v3] " jgart via Guix-patches via
2023-03-30  9:36   ` bug#62393: " Guillaume Le Vaillant

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=87leji366i.fsf@kitej \
    --to=glv@posteo.net \
    --cc=62393@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    /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).