Skip to content
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

[Feature request] Generate relative path hashes #10

Open
vatterspun opened this issue Nov 25, 2018 · 4 comments
Open

[Feature request] Generate relative path hashes #10

vatterspun opened this issue Nov 25, 2018 · 4 comments

Comments

@vatterspun
Copy link

vatterspun commented Nov 25, 2018

Current behavior

The program writes JSON files to static file destinations e.g. c:\test\file.txt ... this is very useful because it's always easy to find and check files, but if the folder is removed or the files are moved to a different location/drive, the program will throw errors:

image

Requested behavior

Ability to save to relative folders e.g. c:\verification-file.json which would use links like test\file.txt.

Who would use this?

Individuals checking files on:

  • Cloud sync services
  • Removable media
  • Backups that save to a folder different from the original

Possible issues

This is a non-simple feature request because one of the following must happen:

  • The verification file would need to remain in the same place relative to the folder it's verifying (for example if verifying c:\test, the verify file would need to be on the _c:_ drive. This could be a problem if for example the _c:_ drive isn't accessible as root folder access may be disabled by the admin.
  • The user would need to specify the root folder location. This might be a problem because whether the root folder is _c:_ or c:\test is not clear and the user may have to test a few times to find the correct root or research the contents of the JSON file.
@hellzerg
Copy link
Owner

hellzerg commented Dec 1, 2018

No time to spare in order to implement this now. Life problems.

Sorry my friend.

@vatterspun
Copy link
Author

No time to spare in order to implement this now. Life problems.

Please don't apologize - you couldn't have done better than to give away your hard work along with the source code in a good license. People get busy, sick, and even die in software just like everywhere else. Putting it out there is all we can do.

I would ask that you put something on the main page requesting a new maintainer, if that's applicable.

Thanks and I hope your life issues get resolved. If there's any karma, I hope you see some good fortune for all the effort you've given away for free.

@hellzerg
Copy link
Owner

hellzerg commented Feb 5, 2022

@vatterspun Hello. If you are still there, we can work to complete this feature. But before this, I will need a detailed description.

@vatterspun
Copy link
Author

But before this, I will need a detailed description.

Not sure what to add to my original request to make it more comprehensive. There's static paths like D:\temp\file.md5 and relative like temp\file.md5. Static means that you have to move it to the original path before the files can be evaluated, relative you can put them most anywhere and then just set the root folder (in this case the d:\ drive).

What more info were you looking for?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants