From: telamon <telamon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: milkytracker: added rtmidi for midi support.
Date: Wed, 02 Sep 2020 09:33:58 +0200 [thread overview]
Message-ID: <20200902073358.wpJBZEM62atQr-IilVL5_-IN6iIZn7E6Csnn340CC28@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24427@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
New comment by telamon on void-packages repository
https://github.com/void-linux/void-packages/pull/24427#issuecomment-685412188
Comment:
@ahesford I'll fix the squash, as for the build option I can't really say.
Using milky-tracker without midi-hardware is quite hardcore-retro. Having this as a build option will be a bit hit-and-miss just the same as force enabling the rtmidi dependency would be.
I believe chances are equally high that whoever has an opinion about this item is going to be forced to recompile milky from source.
If I understand the milky-docs correctly then `rtmidi` is it's sole dependency to interact with a midi-signal, there are no other options.
Rtmidi compulsory dependency **pros**
Newbies can just plug in their midi-keyboard, xbps-install milky, start it up and use `aconnect` to patch the midisignal into milkytracker.
**Cons**
People that still use milky without midi-hardware (if-exists) will experience a few extra kilobytes of binary installation size.
Thoughts anyone???
next prev parent reply other threads:[~2020-09-02 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 21:34 [PR PATCH] " telamon
2020-08-22 22:51 ` [PR PATCH] [Updated] " telamon
2020-08-27 14:30 ` ahesford
2020-09-02 7:33 ` telamon [this message]
2020-09-02 16:02 ` ahesford
2020-09-06 21:37 ` [PR PATCH] [Merged]: " ahesford
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=20200902073358.wpJBZEM62atQr-IilVL5_-IN6iIZn7E6Csnn340CC28@z \
--to=telamon@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).