Search Criteria
Package Details: hashdeep 4.4-7
Package Actions
| Git Clone URL: | https://aur.archlinux.org/hashdeep.git (read-only, click to copy) |
|---|---|
| Package Base: | hashdeep |
| Description: | cross-platform tools to message digests for any number of files |
| Upstream URL: | https://github.com/jessek/hashdeep |
| Licenses: | GPL, custom |
| Submitter: | gromit |
| Maintainer: | None |
| Last Packager: | gromit |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2024-03-20 14:39 (UTC) |
| Last Updated: | 2024-03-20 14:40 (UTC) |
Dependencies (1)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
Required by (1)
- ksvnupdater (optional)
Latest Comments
dkaylor commented on 2024-04-08 03:37 (UTC)
@tee
Agreed, time to move on. rhash in [extra] looks like an excellent replacement.
tee commented on 2024-03-29 11:36 (UTC)
@dkaylor
Time to move on, unless you want to fork and maintain the project.
dkaylor commented on 2024-03-27 21:07 (UTC)
I used to maintain this in the AUR (when it was called md5deep) before it was promoted to [community]. Thinking of adopting again. However, the upstream appears to be either dead or very dormant. There are pending pull requests from years ago and issues with no response.
Having said all that, I use it often, mainly due to the directory recursion ability. I only use it for producing sha256 and sha512 hashs.
So wondering what others think: Worth trying to maintain or time to move on?