On Wed, Mar 06, Johannes Hofmann wrote:
On Tue, Mar 05, 2013 at 11:35:02PM +0100, Sebastian Geerken wrote:
"man dillo" shows
In order to use the hyphenation feature, pattern files from CTAN need to be installed to ${prefix}/lib/dillo/hyphenation/. This can be done with the script install-hyphenation. Call it with ISO-639-1 language codes as arguments, or without arguments to get more help.
"${prefix}" should be replaced here.
Yes. Does someone know how this is best done with automake?
Move doc/dillo.1 to doc/dillo.1.in and add this to doc/Makefile.am: diff -r f37ab8cb8930 doc/Makefile.am --- a/doc/Makefile.am Tue Mar 05 19:47:09 2013 +0100 +++ b/doc/Makefile.am Wed Mar 06 22:24:33 2013 +0100 @@ -39,3 +39,6 @@ Selection.txt \ Dpid.txt \ README + +dillo.1: + sed 's%.{prefix}%${prefix}%g' < dillo.1.in > dillo.1 This replaces ${prefix} by the actual value. I could not get the "$" into the sed expression (therefore the "."), so this is not perfect.
Also we would need to install the install-hyphenation script, so that it becomes part of binary packages.
There would also some changes neccessary, since the script searches "Makefile".
This is an aspect I have not yet thought about: whether the script is part of the installation process (as now) or the installation itself (as you suggest).
If we install it it will probabely end up in binary packages and be available for end users. If we don't install it, we rely on packagers to deal with the problem (e.g. to create a separate hyphenation pattern package).
If we do that it would have to be renamed to dillo-install-hyphenation or something like that. Does this sound ok?
I'll try to modify the script, so it can be installed to ${prefix}/bin. In any case, this is certainly useful.
[...]
OTOH, if someone installs dillo from the tarball, and does not notice that she should download pattern files. Since hyphenation is inactive, when there is no pattern file installed, this feature will be invisible.
That's why I thought to put it into the Makefile, so he sees the notice when he calls "make install". That's what I meant with my question.
We can of course also add the notice to make install, that should not harm anyone.
Although I must admit that this approach only works for one message. Sebastian