[arch-proaudio] snd with scheme
Hi list, I've recently started working with the snd editor (the audacity debacle gave me that last push...), and I was just wondering what the rationale is for shipping snd with ruby support, instead of the default scheme? Would it be an idea to keep the snd package in community with the scheme default, and instead create a snd-{ruby,forth} package in aur instead for those that use those? Best, Kenneth -- Roosna & Flak - Contemporary Dance & Music Web: roosnaflak.com Code: {github,gitlab}.com/kflak Mastodon: @kf@sonomu.club
Hi, AFAIR this (snd-ruby...) was the way it was handled in debian distros when I still was on debian. It might be that on debian you had to symlink snd to snd-scheme, but my memories are blurred. I'd appreciate, if snd would stay in sync with the scheme default but it's not a big deal. -- Orm Am Samstag, den 10. Juli 2021 um 07:15:27 Uhr (+0000) schrieb Kenneth Flak via arch-proaudio:
Hi list,
I've recently started working with the snd editor (the audacity debacle gave me that last push...), and I was just wondering what the rationale is for shipping snd with ruby support, instead of the default scheme? Would it be an idea to keep the snd package in community with the scheme default, and instead create a snd-{ruby,forth} package in aur instead for those that use those?
Best, Kenneth
-- Roosna & Flak - Contemporary Dance & Music Web: roosnaflak.com Code: {github,gitlab}.com/kflak Mastodon: @kf@sonomu.club
Yup, the default would definitely be preferable. In arch it is simply a flag in the pkgbuild and a dependency that can be removed. I maintain my own pkgbuild locally that I occasionally sync up to the community one. It currently looks like this:
```
# Maintainer: David Runge
Hi,
AFAIR this (snd-ruby...) was the way it was handled in debian distros when I still was on debian. It might be that on debian you had to symlink snd to snd-scheme, but my memories are blurred.
I'd appreciate, if snd would stay in sync with the scheme default but it's not a big deal.
-- Orm
Am Samstag, den 10. Juli 2021 um 07:15:27 Uhr (+0000) schrieb Kenneth Flak via arch-proaudio:
Hi list,
I've recently started working with the snd editor (the audacity debacle gave me that last push...), and I was just wondering what the rationale is for shipping snd with ruby support, instead of the default scheme? Would it be an idea to keep the snd package in community with the scheme default, and instead create a snd-{ruby,forth} package in aur instead for those that use those?
Best, Kenneth
-- Roosna & Flak - Contemporary Dance & Music Web: roosnaflak.com Code: {github,gitlab}.com/kflak Mastodon: @kf@sonomu.club
On 2021-07-10 07:15:27 (+0000), Kenneth Flak via arch-proaudio wrote:
I've recently started working with the snd editor (the audacity debacle gave me that last push...), and I was just wondering what the rationale is for shipping snd with ruby support, instead of the default scheme? Would it be an idea to keep the snd package in community with the scheme default, and instead create a snd-{ruby,forth} package in aur instead for those that use those?
Hi Kenneth, sorry for the late reply. I have been fairly busy with other aspects of the distro lately. Could you elaborate on why it is problematic for your workflow to have the ruby dependency? From what I can see snd is able to use either of the additional extension languages (such as ruby [1] or forth [2]) when compiled with them. Maybe I don't understand the limitations of the program/build system correctly, but although the configure step [3] seems to imply an "either/or" situation with the extension language, it is not really clear as to what this means in regards to the extension language and the scheme default. FWIW: With current snd in the repos I am able to open ruby or scheme based files (admittedly there's still a ruby gem missing for cmath though). Best, David [1] https://ccrma.stanford.edu/software/snd/snd/grfsnd.html#sndandruby [2] https://ccrma.stanford.edu/software/snd/snd/grfsnd.html#sndandforth [3] https://ccrma.stanford.edu/software/snd/snd/grfsnd.html#sndconfigurationswit... -- https://sleepmap.de
Hi David, FYI: I'm using snd with scheme and couldn't use the packaged version of arch as it seems to have ruby built in. I'm now using a self compiled snd version with scheme in /usr/local, but maybe it'd be good to do it like debian and also package a snd-scheme in arch for people like me. IIRC debian has snd-ruby, snd-forth and snd-scheme (meybe even creating a symlink to snd to make them coexist nicely instead of replacing the snd binary, but my memories are fading). Best, Orm ---------------------------------------------------------------------- Prof. Orm Finnendahl Komposition Hochschule für Musik und Darstellende Kunst Eschersheimer Landstr. 29-39 60322 Frankfurt am Main https://www.youtube.com/watch?v=2rWha1HTfFE&list=PLiGfneJSWmNw6dTUvcTHbTkCYOOTiB_N6 Am Dienstag, den 10. August 2021 um 10:12:11 Uhr (+0200) schrieb David Runge via arch-proaudio:
On 2021-07-10 07:15:27 (+0000), Kenneth Flak via arch-proaudio wrote:
I've recently started working with the snd editor (the audacity debacle gave me that last push...), and I was just wondering what the rationale is for shipping snd with ruby support, instead of the default scheme? Would it be an idea to keep the snd package in community with the scheme default, and instead create a snd-{ruby,forth} package in aur instead for those that use those?
Hi Kenneth,
sorry for the late reply. I have been fairly busy with other aspects of the distro lately.
Could you elaborate on why it is problematic for your workflow to have the ruby dependency? From what I can see snd is able to use either of the additional extension languages (such as ruby [1] or forth [2]) when compiled with them.
Maybe I don't understand the limitations of the program/build system correctly, but although the configure step [3] seems to imply an "either/or" situation with the extension language, it is not really clear as to what this means in regards to the extension language and the scheme default.
FWIW: With current snd in the repos I am able to open ruby or scheme based files (admittedly there's still a ruby gem missing for cmath though).
Best, David
[1] https://ccrma.stanford.edu/software/snd/snd/grfsnd.html#sndandruby [2] https://ccrma.stanford.edu/software/snd/snd/grfsnd.html#sndandforth [3] https://ccrma.stanford.edu/software/snd/snd/grfsnd.html#sndconfigurationswit...
On 2021-08-10 10:41:11 (+0200), Orm Finnendahl via arch-proaudio wrote:
Hi David,
FYI: I'm using snd with scheme and couldn't use the packaged version of arch as it seems to have ruby built in. I'm now using a self compiled snd version with scheme in /usr/local, but maybe it'd be good to do it like debian and also package a snd-scheme in arch for people like me. IIRC debian has snd-ruby, snd-forth and snd-scheme (meybe even creating a symlink to snd to make them coexist nicely instead of replacing the snd binary, but my memories are fading).
I understand. I'll try to look into a split package then. It is unfortunately not very clear from the build system's point of view how to handle the extension language(s). After all, all example files are automatically installed to /usr/share/snd/ (e.g. .scm, .rb and .fs) further implying to the user that all languages are supported. This is very confusing behavior IMHO. Best, David -- https://sleepmap.de
On 2021-08-10 11:04:28 (+0200), David Runge via arch-proaudio wrote:
On 2021-08-10 10:41:11 (+0200), Orm Finnendahl via arch-proaudio wrote:
Hi David,
FYI: I'm using snd with scheme and couldn't use the packaged version of arch as it seems to have ruby built in. I'm now using a self compiled snd version with scheme in /usr/local, but maybe it'd be good to do it like debian and also package a snd-scheme in arch for people like me. IIRC debian has snd-ruby, snd-forth and snd-scheme (meybe even creating a symlink to snd to make them coexist nicely instead of replacing the snd binary, but my memories are fading).
I understand. I'll try to look into a split package then.
I have now added an updated snd package to [community-testing], which supports both extension languages by providing two executables (snd-s7 and snd-ruby), but symlinks snd-s7 to snd (so the default extension language is also the default when just calling snd). Using a split package for this turned out too messy. Please check whether this works for you as expected. I have removed extension language files that are not compatible with the respective snd versions, added specific and updated XDG desktop integration files, added ruby to optdepends and updated to 21.6. Best, David -- https://sleepmap.de
Sounds great, David! I'm a bit wary of enabling the testing repos. Is there a way to selectively download only the snd pkgbuild from there? Best, Kenneth -- Roosna & Flak - Contemporary Dance & Music Web: roosnaflak.com Code: {github,gitlab}.com/kflak Mastodon: @kf@sonomu.club On 20 Aug 2021 11:31, David Runge via arch-proaudio wrote:
On 2021-08-10 11:04:28 (+0200), David Runge via arch-proaudio wrote:
On 2021-08-10 10:41:11 (+0200), Orm Finnendahl via arch-proaudio wrote:
Hi David,
FYI: I'm using snd with scheme and couldn't use the packaged version of arch as it seems to have ruby built in. I'm now using a self compiled snd version with scheme in /usr/local, but maybe it'd be good to do it like debian and also package a snd-scheme in arch for people like me. IIRC debian has snd-ruby, snd-forth and snd-scheme (meybe even creating a symlink to snd to make them coexist nicely instead of replacing the snd binary, but my memories are fading).
I understand. I'll try to look into a split package then.
I have now added an updated snd package to [community-testing], which supports both extension languages by providing two executables (snd-s7 and snd-ruby), but symlinks snd-s7 to snd (so the default extension language is also the default when just calling snd). Using a split package for this turned out too messy.
Please check whether this works for you as expected.
I have removed extension language files that are not compatible with the respective snd versions, added specific and updated XDG desktop integration files, added ruby to optdepends and updated to 21.6.
Best, David
Hi list, Just wanted to flag something I discovered the hard way: In order to make snd load extensions without crashing, it needs fonts from the https://archlinux.org/packages/extra/any/xorg-fonts-misc/ package, so I suppose this should be listed as an (optional) dependency. Best, Kenneth -- Roosna & Flak - Contemporary Dance & Music Web: roosnaflak.com Code: {github,gitlab}.com/kflak Mastodon: @kf@sonomu.club On 20 Aug 2021 09:58, Kenneth Flak via arch-proaudio wrote:
Sounds great, David!
I'm a bit wary of enabling the testing repos. Is there a way to selectively download only the snd pkgbuild from there?
Best, Kenneth
-- Roosna & Flak - Contemporary Dance & Music Web: roosnaflak.com Code: {github,gitlab}.com/kflak Mastodon: @kf@sonomu.club On 20 Aug 2021 11:31, David Runge via arch-proaudio wrote:
On 2021-08-10 11:04:28 (+0200), David Runge via arch-proaudio wrote:
On 2021-08-10 10:41:11 (+0200), Orm Finnendahl via arch-proaudio wrote:
Hi David,
FYI: I'm using snd with scheme and couldn't use the packaged version of arch as it seems to have ruby built in. I'm now using a self compiled snd version with scheme in /usr/local, but maybe it'd be good to do it like debian and also package a snd-scheme in arch for people like me. IIRC debian has snd-ruby, snd-forth and snd-scheme (meybe even creating a symlink to snd to make them coexist nicely instead of replacing the snd binary, but my memories are fading).
I understand. I'll try to look into a split package then.
I have now added an updated snd package to [community-testing], which supports both extension languages by providing two executables (snd-s7 and snd-ruby), but symlinks snd-s7 to snd (so the default extension language is also the default when just calling snd). Using a split package for this turned out too messy.
Please check whether this works for you as expected.
I have removed extension language files that are not compatible with the respective snd versions, added specific and updated XDG desktop integration files, added ruby to optdepends and updated to 21.6.
Best, David
participants (3)
-
David Runge
-
Kenneth Flak
-
Orm Finnendahl