Oh, btw, I’m considering building a VCS. The whole repository is just a single big patch file. It’s for small projects tho. Ideas on what problems I might encounter with this approach?
@abucci@anthony.buc.ci Is the repo plain text?
My VCS would allow you use standard UNIX tools like diff and patch.
Example repo for my VCS
@abucci@anthony.buc.ci Ah, I remember at leas one issue I had with Pijul. Rust….
I’m installing now, It’s not the first time. I remember tho I wasn’t satisfied with their repo format.
Yeah, errors on cargo install pijul --version "~1.0.0-beta"…
@abucci@anthony.buc.ci Ran it on OpenBSD, running it on Linux now.
Error compiling nix. Crap, so complicated! See, that’s why I’m building a VCS and not doing React.
@adi@twtxt.net What’s wrong with Git?
@prologic@twtxt.net I’m not a big fan of the CLI interface!
And I’d rather have a plain text repo!
@adi@twtxt.net Why not write a new CLI? Git nowadays is just an underlying storage format and library. Consider using jesseduffield/lazygit: simple terminal UI for git commands for example.
@prologic@twtxt.net Yeah, I’m considering a simpler storage format.
Like this https://envs.sh/hzH.diff, it’s a single patch file.