and then make that file format exactly the same as .gitignore
but yeah, im just brainstorming
How about putting these options behind feature flags? So that those who don't want to depend on git don't have to.
Currently bupstash only really mentions tar and ssh
in any documentation
But I understand your concern. Git won't be there forever, like SVN wasn't. But also, it won't just disappear within the next decade, and how old do you expect Bupstash to get before a new flashy rewrite comes up?
I would like bupstash to work for 20 years at least
maybe foolish :D
if the concept of a filesystem changes too much lol
it would be nice if i could rewrite bupstash from scratch in a different language and not regret much
but yeah, i also don't want to be spartan to the point of inconvenience
I don't doubt it'll work that long. But I'm not sure if you'll still want to use it by then. Think of what backup tooling we had 15 years ago. Does it still work today? Yeah, probably. Do we still want to use it? Now that bupstash exists? :D
and tarsnap has been going for about 10 years now lol
but yeah
the flashier a tool is, the less likely it is to survive imo
of course, if something significantly better appears
its fine to migrate
That's one of those moments where I'd really like to see a solid Rust plugin system
the OG version control system
that is part of the POSIX standard iirc
.gitignore format is a nice format though
2 replies
bupstash already supports glob exclusions
and .gitignore is just more glob exclusions
globbing is a (more or less) timeless concept haha
although smartphones etc are getting rid of /tree filesystems
or hiding them a lot :P
Ah and I forgot: there are multiple ignore sources, which have to be merged in specific order because order matters https://git-scm.com/docs/gitignore
The absolute simplest option is to give 'bupstash put' a --filelist option
and then you can use whatever crazy multithreaded filewalker to list them
this is not mutually exclusive with other things though
bupstash put --file-list :: ./files.txt
And I think we can also copy the
--exclude-if-present ".nomedia" argument 1:1
i think thats fine
(I don't want to copy borg too much, mainly becaues i felt like it was option soup)
or was that restic lol
but when I used borg I did use exclude markers
but I am the most biased person to judge that
I agree with you, although I really like Borg's approach to excludes handling (except for the part where you can choose which formats to provide your paths in the exclude file with, i.e. plain path vs glob vs regex etc.)
Also, exclude files need a way to handle newlines in file paths (: (the POSIX way would be to use NUL as separator instead)