Extension Development :: gnu-utils



You had me scratching my head for a minute just now. While messing around with the wget extension I thought I'd check its info file (not the mydsl info, but the texinfo) to see how easily it would be to convert it to a format that could be easily read in DSL (the wget info provides a lot more information than the man page).  To my surprise it displayed natively, or so it seemed.  After a minute I thought to check it and it turned out that info is included with compile-3.3.5

I'm wondering if this is necessary.  Info is definitely a good app to have, but does it have anything to do with compiling?  It might be better suited as a separate extension.

Sorry I've been putting a lot of focus on compile here, when the topic should be gnu-utils.
Quote
I'm wondering if this is necessary.  Info is definitely a good app to have, but does it have anything to do with compiling?  It might be better suited as a separate extension.
- I seem to remember Curaga also mentioned this. I believe this comes from texinfo. It was added because a few apps I've compiled required texinfo before they would compile without errors. Perhaps the need could be avoided by the appropriate use of --disable-docs type switches?

Quote
Sorry I've been putting a lot of focus on compile here, when the topic should be gnu-utils.
- No problem, I already learnt several things from this thread.
They actually often won't even check for texinfo, they just assume it exists.
My way around it, when I don't need the info files, is creating this as "makeinfo":
Quote
#!/bin/sh
exit 0

This satisfies the rude packages, as well as the well mannered ones that actually check for texinfo.
Some info pages are still installed, but they can be removed easily.
On a semi-off-topic note, I found that info files are easily read in a text editor. It seems that the formatting done to them is little more than splitting the file into pages.

While I dislike the navigation (or apparent lack of it) in Info, they often provide much more information than man pages do, so when info pages are created I tend to keep them on hand.
I've been experimenting with compiling without gnu-utils loaded - several apps require the full version of sed to compile and some apps require something (the error message does not say what) in gnu-utils to compile.

So, the morale of the story seems to be that coreutils - plus findutils and a couple of other things would be a useful tool.
Next Page...
original here.