-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Save space by hardlinking instead of copying #546
Comments
That sounds like a good idea. Instead of hard links, I'd suggest soft links though. Because these work across file system boundaries. The steps to achieve this would be:
Are you interested in implementing this? |
I for myself think hardlink is better because it won't be affected if the originals are deleted or moved, which works more transparently and can be the default option, benefiting most users without affecting their usage. If hardlink can't be created, be it because the OS doesn't support or because it crosses filesystem boundaries, it fallbacks to copying. A switch to enable softlink can be an enhancement independent of this: it works on more situations, but requires user's attention. What do you think? |
Then we should just have two options perhaps, |
It would be nice if inside of
view_xxxx.mve
directory, the fileoriginal.jpg
was a hardlink of the original, instead of copy (when possible). This would save hard disk space.The text was updated successfully, but these errors were encountered: