Feel free to contact me at my username at foldling.org, or visit my homepage for more info.
This approach will work for the runtime and core programs (chicken, csc, and csi), but the extension-related tools (chicken-install, etc.) have some assumptions baked in that prevent this trick from working seamlessly. Specifically, the build and install scripts generated during egg installation assume PREFIX is an absolute path.
Leaving this ticket open as it's a nice idea, but that will need to change before this can progress.
Marc Feeley shared a nice hack that may allow the archives distributed by Dust to be used without patching.
It would be nice if symlinks in the
.builds/directory were followed, so that they trigger builds just the same as regular files.
My use case for this is a project with multiple components, and multiple manifests for each component, so the files are laid out like so:
.builds/ foo.yml -> ../builds/foo/primary.yml bar.yml -> ../builds/bar/primary.yml builds/ foo/ primary.yml secondary.yml bar/ primary.yml secondary.yml
This way I can keep all build manifests together, and have some subset of them run automatically when commits are pushed.
Currently, this setup throws the following error. It looks like builds.sr.ht isn't dereferencing the symlink, and is trying to parse the link target as YAML instead:
$ git push origin test Total 8 (delta 0), reused 0 (delta 0), pack-reused 0 remote: Error submitting build job: bar.yml: yaml: unmarshal errors: remote: line 1: cannot unmarshal !!str `../buil...` into main.Manifest To git.sr.ht:~evhan/example * [new branch] test -> test
Sidenote, these last few ticket updates were triggered via the CLI like so:
$ sourcehut update ticket chicken-sourcehut 1 --comment=- $ sourcehut update ticket chicken-sourcehut 1 --status=resolved --resolution=implemented
No worries, I've added this to the latest version.
I don't know much about Guix but I'd be happy to help get it running there, or try to package it if that would be useful.
Hey ~alextee, did you happen to get a start on this? I'll probably take a swing at it here over the holidays, but let me know if you're already working on it.
ticketprocedure currently supports retrieving tickets, but not adding or modifying them. It should be extended to work with the
I've added a
dust disablecommand that turns off the active CHICKEN version. This is included in version 0.0.13. Please give it a try and reopen this ticket if it doesn't work for you.
Thanks again for the suggestion!