From 71405c1c85e0442b2d2ba5b16527439fa2bf2397 Mon Sep 17 00:00:00 2001 From: tobiasBora Date: Wed, 2 Oct 2019 21:20:36 +0000 Subject: [PATCH] --- ...escribe_a_file_in_function_of_another_file.mdwn | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/todo/Describe_a_file_in_function_of_another_file.mdwn diff --git a/doc/todo/Describe_a_file_in_function_of_another_file.mdwn b/doc/todo/Describe_a_file_in_function_of_another_file.mdwn new file mode 100644 index 0000000000..54bd0d4980 --- /dev/null +++ b/doc/todo/Describe_a_file_in_function_of_another_file.mdwn @@ -0,0 +1,14 @@ +Hello, + +In order to save space/bandwith/... I would like to create a way to describe a file compared to another. You could see this as a kind of very special "remote" (which is local :P), that says "To produce file XXX, take file YYY, and run command CCC with args YYY". + +You may ask why it is useful? I have several usecases: + +1) my first usecase is that I would like to be able to generate thumbnails for my pictures in order to speed up display. A thumbnail can be easily created from a picture (with for example the convert command), but when you don't need the thumbnail, you may prefer to remove them locally to save space. +2) similarly, I have some RAW photo files, and a script to turn them into .JPG file. Or even better, I could have several scripts to convert my initial RAW files into several .JPG files, with different parameters/look. Keeping both RAW and developed JPG can be heavy, so this kind of tool could allow me to remove the .JPG file(s) when I don't need them anymore, so I don't mind to drop the .JPG file as soon as the RAW does exist (but if the RAW does not exist anymore, I shouldn't be able to remove the .JPG of course). +3) I also have on my desktop some compressed files (.iso for example, or old projects). Most of the time, I don't really need to keep the uncompressed .iso, but from time to time, I may need them. For now I manually uncompress them, use them, and delete them... But it could be cool to let git-annex deal with them automatically. + +Does git-annex provide such functionnality? If not, do you think it could be implementable? + +Thanks! +