@neauoire Big project move!
(Looking at the contributors, you show up 3 separate times. All the instances point to the same sr.ht profile but I wonder what caused it...)
@drisc Different computers/certificates over a few years. :)
@neauoire Ah yeah, that would do it. Also looks like different emails cause it as well in Nicola's case.
@neauoire is that Elementary?
@neauoire nice to see it's built with make now. packaging was a bit awkward with the old script. i should look into it again... sometime. (so many guix projects )
@neauoire ...oh nooo it just calls the script.
well. i guess it will work.
@grainloom it's really easy to build orca, I can't imagine what could cause an issue.
@neauoire well, i was more unexperienced and didn't trust the script to do feature autodetection correctly on such a foreign distro.
it's a rather idiosyncratic build system that takes a while to untangle.
and packages that use pre-defined build systems can use some package transformations, so i was hoping it would get a makefile eventually.
but now that i know more about building stuff, i think it should work.
@grainloom If you prefer, you could use it on 9Front instead?
@neauoire i wanted to package it for others too. i might use it on 9front, but i was hoping some other Guix users will give it a try too.
@grainloom which virtual synths do people on guix usually use?
@neauoire that's a very good question that i wish i knew the answer to.
there does seem to be quite a few results in `guix search synth | less`.
ed.: fluidsynth, whysynth, cursynth, amsynth, probably a bunch of others.
@neauoire eg.: lots of build systems honor the #:make-args field of package-arguments. so if someone wanted to build their whole system with clang instead of gcc, they would start out by writing a function that returns modified packages that include a CC=clang make argument.
it's not something people do in practice just yet (AFAIK at least), but something i'd like to try at some point, so it's not a huge deal.
it's mostly just that i'm (very) slightly worried if breaking from the conventions other packages follow is gonna be a disadvantage to others who might want to modify their packages. like compile everything with certain CFLAGS enabled. -fsanitize=address, that kind of stuff. but it's whatevs.
i also didn't quite understand how Guix's pre-defined build systems worked and how ./tool doing its own CFLAGS would affect it. now i know that it won't break the build, just make automatic customization harder. (because stuff like LIBRARY_PATH aren't touched.)
@grainloom Did you make a guix package for orca?
@neauoire yup, trying to test now.
it definitely works to some degree.
just wanna test MIDI.
@grainloom okay! the master fork on sr.ht was slightly behind by a few commits, I wanna make sure that you have all the bits :>
🤦♀️ I was in a fork when I did the migration.
@neauoire it looks like i have no idea how MIDI works.
@grainloom Are you trying to implement MIDI yourself? or do you have no idea how orca's midi works?
@neauoire There's a reference to the old github repo in the README, under "install & run" 👍
@gueorgui cheers! I'll correct.
Merveilles is a community project aimed at the establishment of new ways of speaking, seeing and organizing information — A culture that seeks augmentation through the arts of engineering and design. A warm welcome to any like-minded people who feel these ideals resonate with them.