Benjamin Kane
Benjamin Kane
Then the subsections could be: ``` fling starlark link/unlink fling tree link/unlink ```
I could use something like what drone does: https://docs.drone.io/pipeline/scripting/starlark/ My ctx object coul have fields like platform, hostname, user, tags that my starlark config could branch on
Could also have one dimensional labels and a `help(ctx)` function that returns a string to be printed by fling
I could also switch to https://github.com/SuperCuber/dotter . It uses TOML overwriting that doesn't look too crazy.
@xiantang , I'm not sure this is a good first issue because, even though it's easy, it requires a new Homebrew formulas repo to be made and permissions to be...
https://github.com/charmbracelet/vhs might be useful here too
Oh, I didn't realize Pipelight wasn't cross-platform. Would you accept a PR highlighting that in the README?
Also, are there any plans to make Pipelight cross-platform? Nothing in the description seems like its Linux-specific- I'm curious what Linux features Pipelight uses that aren't in MacOS or Windows
I'm not a rust dev, but if I check it out, can I run `cargo test` to run the tests?
Unfortunately, the `procfs` crate still doesn't work on MacOS: ``` $ cargo build -- snip -- Compiling async-trait v0.1.74 error: failed to run custom build command for `procfs v0.15.1` Caused...