ispell-autobuildhash [--force] Options: --debug Show some extra ispell-autobuildhash information. --dry-run Show what would be done, but do nothing real. --force Rebuild the hash file for all dicts providing a compat file skipping the test. --triggered Tell the script that is run in the triggers stage.
--debug Show some extra ispell-autobuildhash information. --dry-run Show what would be done, but do nothing real. --force Rebuild the hash file for all dicts providing a compat file regardless of the compatibility levels found. --triggered Tell the script that is run in the triggers stage. When run under dpkg control, do not try to set the 'ispell-autobuildhash' trigger, but run real B<ispell-autobuildhash> code. When not run under dpkg control, real code will always be run and '--triggered' option has no real effect.
The most common case is having a single source. In this case you must put the $dict.aff file at /usr/lib/ispell/$dict.aff as usual and the munched wordlist compressed with gzip at /usr/share/ispell/$dict.mwl.gz.
This script supports the way ipolish allows selection of subdictionaries to be put in the hash file. It will detect the presence of the main language .desc file and call update-ipolish-hash as appropriate.
Although this script looks for the existence of a update-ispell-hash script with supposedly similar functionality to update-ipolish-hash, this latter does not really exists, although it might be added at some time to ispell or to the dictionaries-common system, if enough demand is found.
If your package provides more than one ispell dictionary you will need to do the steps above for each dictionary.
Dictionaries-common scripts will call internally this script and create a hash file at /var/lib/ispell/$dict.hash. You must set a symlink to that file from /usr/lib/ispell/$dict.hash. You are also suggested to create an empty file at /var/lib/ispell/$dict.hash in the install target of your package build process. This empty file will be overwritten when the real hash is created, but will make the hash be removed at package removal without any magic being done in the postrm and will also help to keep track about which package owns that file.
If you use debhelper you may want to pass -Xvar/lib/ispell option to dh_md5sums call in your debian/rules file, to avoid debsums complaining about those hash and compat files.
ispell maintainer should also call this script from package postinst. When comparing versions it will get the ispell version from file /usr/share/ispell/ispell.compat, or if it does not exists, from the upstream version as given in the first line of 'ispell -vv output.