@neauoire :moar: 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 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 :blobsob: )

@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.

@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.

@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.

@cancel @neauoire hmm. with make i guess it works, as long as definitions are converted to environment variables.
but afaik ./tool CC=clang is not the same as CC=clang ./tool.

@grainloom @neauoire ./blah CC=clang is not how environment variables are defined by any shell I know of

@cancel @neauoire
try this:

echo 'env-dump:' > Makefile
echo -e '\tenv' >> Makefile

env will dump the environment to stdout.

now run `make env-dump MYVAR=MYVAL | grep MYVAL`

@cancel @neauoire although i guess make doesn't count as a shell, so you're right.

@grainloom @neauoire make must do some weird stuff to allow you to pass env settings as flags... I don't know why you want this?

@cancel @neauoire not sure it's weird, it's probably easier than custom variables storage. this is also how Plan 9's rc shell works by the way.

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 @neauoire well, you can make your own build thing for orca-c, if you want. There's only a few source files.

I'm not going to put a build system into the orca-c repo other than the tool script that's already there. You'd have to kick me off the project. :)

@cancel @neauoire ok so i'm mostly done with the package, but... what do i name it?
there is already an Orca package for the screen reader.

@cancel @neauoire also, should i put the sourcehut repo in the home-page field or the 100 Rabbits one?

@grainloom @cancel the sourcehut page, I'll make sure this page has all the links and documentation necessary to find the tutorial and manuals necessary.

@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.

@grainloom Are you trying to implement MIDI yourself? or do you have no idea how orca's midi works?

Show more

@neauoire There's a reference to the old github repo in the README, under "install & run" 👍

Sign in to participate in the conversation

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.