-
Notifications
You must be signed in to change notification settings - Fork 25
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
How to Add Multiple Files and Folders to an Archive Using a Single Command #136
Comments
-input |
thanks |
Another question: for example; And when listing the archive contents:
Output:
|
-find and -replace |
I think there might be a bug: (working) Nothing happens. |
...Because you are using Windows Please try, with the upgrade -force, the current 60.8b. |
It's working, thank you for your effort! There's one more thing: For example, when running this command multiple times: but, I guess, there should be warning, like; |
-find/replace will start again the archiving |
thx |
Hello again, I want to preserve the existing files in the folder when adding new files using the "-to" switch. How can I do that? For example, I run these commands in order: |
They are not removed |
I understand, It works like folder synchronization. I was asking if there's a way to turn that off. I only want to include conflicting files in the process. This issue happens when adding folders, but not when adding files one by one. Also, using the -until switch makes version control quite difficult for automation. Thank you for your interest and support. |
I don't quite understand what you want to do.
|
Why do you want the very same folder? |
I have to use the -to switch; otherwise, I would have to move all the files into a single folder named 'folder,' (before of using zpaqfranz), which is not practical. Why do I need this? I need drag-and-drop functionality, similar to a GUI version of an archiver. So, if I drop files into a folder (inside the archive), I need the -to switch. |
I know zpaq doesn't work with this logic, but it already has the -to capability, even though it only works partially. |
This is weird but I can add a -nodelete switch |
If this causes the growth, I don't know if it is a 'smarter' way. |
Franco, reading this post, I am truly amazed at how you remember so many options. I guess the source code is often your help ;) But where can we also read more in detail about them? Specifically, the -input option caught my attention. It's not in the Wiki, but that's where the detailed documentation should be, where a person can open it and read everything about option 'a' in depth. In the command line help, it's mentioned in five words, but that help is too concise for someone to learn from it. It's more for reference, to remind oneself if they already know what they're doing. The issue with -input -find -replace wasn't clear to me what it's caused by, but it gets resolved with -to. It really seems more intuitive and clear with -find and -replace, but if it doesn’t work... when and why, at least, I didn't understand... that should go to help, with examples, cases and their solution. The proposed new option -nodelete... it can't be explained in one line. I understood what it's for, but with just one line, it won't be clear ;) |
You can try |
I wrote them, so it is not that difficult. What is difficult are the portions written by Mahoney
Usually I write a couple of lines in the Release
True
wow, you really want a big explanation of how zpaq file nomenclature works, and zpaqfranz extensions?
I'll write it down in the meantime, then we'll see if it's of any use, in which case I'll write two lines 😄 |
Just a note. Mahoney is certainly a genius at writing compression algorithms, but he knows virtually nothing about backups; it's not his “world.” This causes zpaq to be born with serious flaws, and incredible complications. |
BTW
|
You can try the pre-release 60.8e via a zpaqfranz -upgrade -force YOU must handle filename collisions
On
You get
|
TRANSLATION You will get something like
meaning that the file 1.txt is "overwritten" in the 2nd version (you can take it from the first, in this example) |
OK, 60.8h just uploaded, with yellow warnings and red errors |
We can make a deal https://github.com/fcorbelli/zpaqfranz/wiki/Voodoo-switches |
Thanks! |
Franco, with pleasure, but where should I write and where should I ask? Here in Issues? |
I can make the wiki writeable by anyone |
Thanks, everything seems to be working fine with the -nodelete switch. I have a few suggestions: If you think collision management is important (it’s not for me), you could introduce two different switches (instead of just -nodelete): -preserve (like -nodelete, but with collision, so it overwrites) These are just suggestions; I’m happy with -nodelete By the way, does using the -range 0:9999999 switch achieve the same effect as -nodelete?" Also, I would like to discuss some details about "-input" switch tomorrow. |
I definitely would like to help with docs |
Wiki is now (should be) open to everyone |
(...) not at all
???
|
"-input" has great potential and is quite practical. However, we need a switch that provides destination paths, similar to the -to switch. Also; with "-find" and "-replace" switchs, we can't achieve this scenario in one version, and the growth issue occurs. Note;
|
Please test the pre-release 60.8j (via zpaqfranz upgrade -force) The growth problem concerns the ever-increasing possibility of name collisions, having essentially a potentially flat namespace. Incidentally, the list of files is stored, in blocks i, even if they are completely deduplicated (i.e., the data fragments are not written to the data blocks) |
Two issue exists;
|
Actually, these issues aren't very important. I think it would be fine if it worked this way. |
You can restrict, the destination of a file input, must be file path. |
Ahemm... No |
Thanks for your effort. I have a suggestion: For the "-x" switch, you could implement the reverse of these operations. For example:
This is just a suggestion; I don’t need it. |
Ahem... no BTW you should to file to file, and folder to folder filesandfolders.txt
destinations.txt
EDIT: of course it's up to you the \ handling
This is NOT good
wpLogs\ is a folder, but e:\apps\whatsapp\chatlogs.txt is a file |
Thanks, there don’t seem to be any other problems. I didn’t realize that the "-input" and "-destination" switches also work for "-x". |
They works everywhere |
Similar to 7-Zip;
7z a archive.7z @files.txt
files.txt:
The text was updated successfully, but these errors were encountered: