From: iFoundSilentHouse <iFoundSilentHouse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Cardinal
Date: Tue, 09 Apr 2024 17:27:14 +0200 [thread overview]
Message-ID: <20240409152714.B8323240E0@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49739@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
New comment by iFoundSilentHouse on void-packages repository
https://github.com/void-linux/void-packages/issues/49739#issuecomment-2045481219
Comment:
Same thing with vcvrack, but it has less deps at least. One more great thing is that it has licensing info for everything and it's fine.
Maybe I'll start packaging vcvrack instead but to do so I need someone from maintainers to say 1) whether it's fine to use git commits to auto-fetch dependencies 2) what is more preferrable to use: latest release of dependency or git commit that is requested with git --recursive
next prev parent reply other threads:[~2024-04-09 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 4:20 [ISSUE] " deathchimera
2024-04-09 15:13 ` iFoundSilentHouse
2024-04-09 15:27 ` iFoundSilentHouse [this message]
2024-04-09 15:27 ` iFoundSilentHouse
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=20240409152714.B8323240E0@inbox.vuxu.org \
--to=ifoundsilenthouse@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).