all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rick Huijzer <ikbenrickhuyzer@gmail.com>
To: 72142@debbugs.gnu.org
Subject: [bug#72142] [PATCH] add python-rtmidi
Date: Tue, 6 Aug 2024 15:28:14 +0200	[thread overview]
Message-ID: <CAGXOz9Y5W4+yXWQfxKOWDYtPnQ-MvA-Ze-5vtLQTwBVUxHnNdw@mail.gmail.com> (raw)
In-Reply-To: <20240716152423.17557-1-ikbenrickhuyzer@gmail.com>

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

Hi,

I've installed guix-system and did some further testing:

The package seems to work just fine when properly installing jack2,
pipewire (pw-jack) or jack on guix-system (and Fedora). It's possible to
put jack (v1) in the propagated inputs, but that's not that elegant I
suppose. Furthermore all the audio packages I could find in guix include
jack in the same way, at build time and not as a propagated input.

I cannot test this with actual midi hardware, only with the
midiout.open_virtual_port method. But for my use case (using the OLA
suite), the library works fine, even when using real DMX controller
hardware.

So after testing and configuring my system properly, I have found no reason
for a revised patch. If you or someone else wants to take a look at this
patch, please do.

Thanks.

-- 
Kind regards,

Rick Huijzer

[-- Attachment #2: Type: text/html, Size: 1260 bytes --]

  parent reply	other threads:[~2024-08-06 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16 15:23 [bug#72142] [PATCH] add python-rtmidi Rick Huijzer
2024-07-18 15:10 ` [bug#72142] [PATCH v1] Fix formatting, boost not needed in python-rtmidi Rick Huijzer
2024-07-18 16:38   ` jgart via Guix-patches via
2024-07-18 20:54 ` [bug#72142] [PATCH] add python-rtmidi Rick Huijzer
2024-08-06 13:28 ` Rick Huijzer [this message]
2024-09-02 20:07 ` Rick Huijzer

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=CAGXOz9Y5W4+yXWQfxKOWDYtPnQ-MvA-Ze-5vtLQTwBVUxHnNdw@mail.gmail.com \
    --to=ikbenrickhuyzer@gmail.com \
    --cc=72142@debbugs.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.