Thanks, this worked, but initially it didn't compile. The error was that it couldn't find any *.1 files in debian/idba and debian/idba-extra.
However, when I renamed the two folders to idba-man and idba-extra-man, it suddenly worked. Do you have any ideas why this was so?
Yes, it should definitely not go to debian/bin, sorry.
Line 17 in debian/rules [1] says, "for the moment the role of these scripts is totally unknown but they do not seem to be necessary," and proceeds to copy run-unittest.py, scan.py, validate_blat and validate_blat_parallel to usr/lib/idba.
I tried commenting out these lines, and the package seems to work just fine. They seem to be required only during compilation and testing, so they probably shouldn't be installed as binaries in the final user installation. Maybe we could let them be in the lib folder?
I'm not sure, however. Please take a look and let me know if I should change it to docs.
I have added a file called data-source.sh in debian/tests/test-data. Is this the right way to do it?
Also, I obtained the data from their research papers about these tools. What kind of license would be applicable in this case?
I added a few examples by extending the debian/createmanpages script.
I'd perfectly accept some kind of "lazyness" here. I would not mind
uploading the current incomplete status despite of the lintian warnings.
I usually decide according to the "importance" of the tool that needs a
manpage. My motivation was to get "the first three in list" and also
the ones we are using in autopkgtest. Feel free to decide whether you
want a complete set of manpages or not.
Okay. I think the set of manpages we have should be enough, given that the other tools aren't too important.
Thanks for the intro to dh_install, man pages and documentation about packages.
Please let me know if any more work is required on this package.
Regards,
Pranav