hashit hashdeep format does not match original hashdeep output, relative versus absolute path /file names

[clach04]

hashdeep defaults to abs paths, hashit has no options other than relative:

C:\tmp\tempty>C:\programs\md5deep-4.4\hashdeep64.exe  *
%%%% HASHDEEP-1.0
%%%% size,md5,sha256,filename
## Invoked from: C:\tmp\tempty
## C:\tmp\tempty> C:\programs\md5deep-4.4\hashdeep64.exe *
##
8,6dd4566eb245627b49f3abb7e4502dd6,f873eef4f852e335da367d76ce7f1973c15b8ffebf532b064df4bc691cd51a87,C:\tmp\tempty\hello

C:\tmp\tempty>hashit -f hashdeep
%%%% HASHDEEP-1.0
%%%% size,md5,sha256,filename
## Invoked from: C:\tmp\tempty
## $ hashit -f hashdeep
##
8,6dd4566eb245627b49f3abb7e4502dd6,f873eef4f852e335da367d76ce7f1973c15b8ffebf532b064df4bc691cd51a87,hello

NOTE C:\tmp\tempty\hello versus hello.

When using relative mode in hashdeep, hashit still does not match exactly - but this is probably nitpicking 😁

C:\tmp\tempty>C:\programs\md5deep-4.4\hashdeep64.exe  -l -r .
%%%% HASHDEEP-1.0
%%%% size,md5,sha256,filename
## Invoked from: C:\tmp\tempty
## C:\tmp\tempty> C:\programs\md5deep-4.4\hashdeep64.exe -l -r .
##
8,6dd4566eb245627b49f3abb7e4502dd6,f873eef4f852e335da367d76ce7f1973c15b8ffebf532b064df4bc691cd51a87,.\hello

NOTE .\ with hashdeep -l.

[boyter]

Seems sensible to add this in, and possibly as the default. I always run hashdeep with relative paths just to make it easier to calculate afterwards. I can understand why you might want abs for checking on a single system, but thats not something I ever did personally, it was always about shipping a verifiable manifest.

[clach04]

Same here, I prefer the relative. Super low priority.