joerg wrote:LOL, i build the same software for nekoware a few hours ago because a friend of mine need it for building gcc 4.x.
Heh, same here, but the person building gcc was me :) Last time I built mpfr locally just for gcc, but I did whole-tree rebuild now, and thought heck, why not do a proper package :)
joerg wrote:There is a odd thing about "/usr/nekoware-build/share/info/dir" which contains only a description of npfr. But the filename isnt very specific and i think "gmake install" makes something wrong. So its good that your package doesnt contain this file.
This file is a common byproduct of installing info pages. "dir" is a directory with references to all the info pages installed on a system. When it doesn't exist, installation procedure creates a new one.
On my installation, info files are in /usr/nekoware/info; in /usr/nekoware/share/info there is currently only mpfr page. Possibly the installation process is hosed in how it handles info pages.
joerg wrote:Btw. I prefer to assing files from nekoware/share to the sw.eoe subimage because most time it contains stuff which is need for running the binary. Thats not true for npfr but i think "man.manpages" isnt the right place for it.
Well, it's a documentation that serves the purpose very similar to man page. It's in no way necessary for mpfr runtime. I think "man.manpages" suits them well.
Thinking about it, packaging the info file without post-install command "install-info" is wrong, too, because then the info page isn't in "dir". I will fix that, but will first have to experiment with pre/post-install commands a bit, e.g. how it handles package upgrades.