[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Michael Bukin <M.A.Bukin@xxxxxxxxxx> writes:
>> How to other Unix packages manage this?
>
> I think most of them install info files in "install-info" target (and
> build info files in "info" target), and don't add entries to dir file
> anywhere.
That's probably not a bad thing for us to copy, then. Or maybe we should
just try to install the dir entry in the most obvious places, and give up
with a message if we can't find the right files or tools, telling the user
how to set those paths themselves.
> I can confirm that it does not use /usr/local/info by default (there is no
> mention of this directory in the executable). I think linux vendors
> decided that it would be good to have only one dir file for the whole
> system and got rid of default support for several dir files.
Yeah, it looks that way. Argh! You are quite right that setting INFOPATH
makes this work, but it would be a shame if people have to do this before
they can get Allegro docs installed properly.
> suggest linux users to use --infodir=/usr/info configure option (I have
> not tested it yet, but it should work). Then in install-info in case of
> missing dir file just copy empty one from library source, try different
> install-info from standard places, first from path, then from /sbin and
> /usr/sbin, and perhaps handle difference between GNU install-info and
> Debian install-info.
I think we can at least autodetect where install-info lives: just look in
/sbin and /usr/sbin, and if it isn't there, assume it must be on the path.
I'm not so sure about creating a new dir file, though: it seems somewhat
strange that a library install should be setting up such basic parts of the
system, if they don't exist already (for the same reason, making that
symlink also strikes me as a bit of an overkill).
How about, if we don't already have a dir file in the directory where we are
trying to install the info file, just give up on setting this entry? We can
print a message telling the user that there is no info dir, so they need to
either create one and set up their info system to use it, or tell Allegro to
install the info pages somewhere else.
> I think we should modify dir file in the directory where we place info
> file. Overwise we may have entry for allegro, but it might not work,
> because info reader can not find allegro.info (not in default INFOPATH).
A good point, but strangely, this does seem to work. My info reader doesn't
find a dir file in /usr/local/info, but it does find
/usr/local/info/allegro.info, when Allegro is listed in /usr/info/dir. So it
probably would work ok if we just added the entry to /usr/info/dir.
--
Shawn Hargreaves - shawn@xxxxxxxxxx - http://www.talula.demon.co.uk/
"A binary is barely software: it's more like hardware on a floppy disk."