You're right, there is not much to gain from it... it was just a suggestion.

Anyway, I think it would be somekind handful.

For instance, if some developer (lazy like me) doesn't remember the exact use of some syscall, he can look at the manual instead of opening a new terminal or exiting from Scratchbox.

Perhaps, the man may just invoke the man outside Scratchbox...

Regards,

           Claudio


Jussi Hakala wrote:
Additionally, not all the software inside Scratchbox and the devkits are built with the documentation. Some of them are, yes, but it's not guaranteed a particular piece of software has the man pages.

As Kalle pointed out, there's not that much to gain from having man pages inside Scratchbox. Only reason would be cross distribution development, ie. developing for debian under rpm based distributions in which case you might not have access to all the man pages for debian tools...

Regards,

 Jussi
Kalle Vahlman wrote:
2007/6/11, Claudio Scordino <[EMAIL PROTECTED]>:
Hi all,

   does anybody know how to enable the man pages inside Scratchbox ?

Should I install some devkit (different than Debian), or should I do something
else ?

I don't think there is a devkit for man. Usually one just uses the man
pages available *outside* scratchbox, but I guess one could install
man into the target if need be. Note however that it won't find the
devkit's or toolchain's man pages (surprisingly they seem to have
those...) unless the search paths are altered...

With man pages available outside scratchbox and on the net, in my
opinion the trouble to get it working would outweigh the gain.


_______________________________________________
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users


_______________________________________________
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users

Reply via email to