Thank you for working on this (and for updating cpmtools)! I don't think the 2.23-1 binaries are actually using libdsk, though?
I can't actually test the unstable binaries at the moment, but 'ldd' doesn't indicate use of libdsk, and 'strings' includes a string that I don't think would appear in a libdsk build: "POSIX driver accepts no options (build compiled without libdsk)" I don't think cpmtools autodetects libdsk, so just adding it to build-deps isn't sufficient -- I think it's necessary to also invoke configure with '--with-libdsk' (in this case, '--with-libdsk=/usr', I think). You can tell whether you have a libdsk-enabled build (without having a suitable disk image to hand) like this: $ cpmls -T dsk /dev/null Response without libdsk: cpmls: cannot open /dev/null (POSIX driver accepts no options (build compiled without libdsk)) Response with libdsk: cpmls: cannot open /dev/null (No such file or directory) [hmm] Whether the cpmls usage message mentions "[-T libdsk-type]" is another clue, but that's based on #ifdef rather than linking so I trusted it slightly less, given the poor error handling in the configure script. (Beware that the cpmtools configure script won't raise an error if there was some problem finding libdsk; it'll just say "no" and leave the build to fall over.)
