I like David's solution below. Having dir file hand made, or have it
built in the "make dist" implementation, and then put the dir into the
distribution would solve the problem the same way putting the .info
files into the dist has helped.
>>> David PONCE <david.ponce@...> seems to think that:
>> I do not install my info files. I use C-u M-x info RET,
>> typa-typa-typa-typa RET to view the CEDET info files.
>> I don't know what the right thing to do for this is either. It
>> makes sense to have the CEDET package build its own dir file for all
>> internal tools. The info hook at the bottom also could go into the
>> cedet-load script. I haven't used the info directory-list before.
>> I'd like to hear what others think about this install solution.
>I sort of install (move) the CEDET's info files in my ~/info directory,
>I added to the INFOPATH environment variable like this:
>And I use install-info to maintain a "dir" file in that directory.
>To ease installation of the CEDET's info files, maybe we could just do
>the same as Emacs. That is:
>- `make' the CEDET's info files into an "info" sub-directory of the
>- Provide a pre-built "dir" file in that sub-directory. I think it is
> necessary because `install-info' is a system command (it is in /sbin
> on my GNU/Linux system) which is not in the PATH environment
> variable of normal users. Moreover, it is unlikely the "dir" file
> will often change.
>Maybe we could just pre-build the "info" directory, for people who
>don't have a makeinfo command installed?
>Then, It would be just easy to add that directory to INFOPATH (we
>could add something about that to the INSTALL doc).
>Finally, perhaps it would simplify maintenance and distribution to
>move all the CEDET documentation source (*.texi and related files)
>into a common "man" or "doc" sub-directory?
>Just my thoughts.
Eric Ludlam: zappo@..., eric@...
Home: http://www.ludlam.net Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: http://www.gnu.org