It's documented to contain "the names of Info documents that the package installs in %p/share/info", and causes install-info commands to be added to postinst and prerm. I don't know much about how to use install-info, but I do know about inconsistencies. To wit...
The usual case is for simple filenames: InfoDocs: foo.info becomes: postinst: %p/sbin/install-info --infodir=%p/share/info %p/share/info/foo.info prerm: %p/sbin/install-info --infodir=%p/share/info --remove foo.info But some packages contain whole subdirs of infofiles, for example, emacs21 has a lot of %p/share/info/emacs-21/*, and these pkgs write their own install-info commands instead of using the InfoDocs field. We seem to do weird things when InfoDocs values contain slashes: InfoDocs: foo/foo.info becomes: postinst: %p/sbin/install-info --infodir=%p/share/info foo/foo.info prerm: %p/sbin/install-info --infodir=%p/share/info --remove foo/foo.info And an absolute pathname is a subset of this "contain slashes" case. Should postinst always contain full pathname to the .info file, or is relative okay (and if so, should we always use relative whenever possible)? Should prerm always use relative, or should it use "whatever postinst used"? dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
