3d3b6d6646
Naive category implementation. Works somewhat, including part of tests. However, I realize now that perhaps, having unique category names in nescesarry for subcommands. On the other hand, allowing them to be non unique would allow splitting up category definitions. But finding the category in a vec would be slow... ...and I want a lot of categories probably... I'm still working on this... here is one way to do it ᕕ( ᐛ )ᕗ Saved in the git log for posterity. Signed-off-by: Christina Sørensen <christina@cafkafk.com> |
||
|---|---|---|
| src | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CODE_Of_CONDUCT.md | ||
| flake.lock | ||
| flake.nix | ||
| install | ||
| install_debug | ||
| LICENSE | ||
| README.org | ||
gg - git gut
A Rust GitOps/symlinkfarm orchestrator inspired by GNU Stow. Useful for dealing with "dotfiles", and with git support as a first class feature. Configuration is done throug a single yaml file, giving it a paradigm that should bring joy to those that use declarative operating systems and package managers.
Although this isn't really a case where it matters that much for performance, being written in rust instead of e.g. janky scripting languages does also mean it is snappy and reliable, and the extensive testing helps ensure regressions aren't introduced.
That said, we're in 0.0.Z, here be dragons for now.
Installation
$ git clone https://github.com/cafkafk/git
$ ./installConfiguration
If you want a template, you can copy the file from src/test/config.yaml:
$ mkdir -p ~/.config/gg/
$ cp src/test/config.yaml ~/.config/gg/config.yamlYou should seriously change this file before running any commands.
The configuration format will likely break regularly in versions 0.Y.Z.