Ondřej Vašík <[EMAIL PROTECTED]> wrote: >> +This install program copies files (often just compiled) into destinatio= n\n\ >> +locations you choose. If you want to download and install a ready-to-u= se\n\ >> +package on a GNU/Linux system, you should be using a package manager\n\ >> +like yum(1) or apt-get(1).\n\ >> +\n\ >> In the first three forms, copy SOURCE to DEST or multiple SOURCE(s) to\= n\ >> the existing DIRECTORY, while setting permission modes and owner/group.= \n\ >> In the 4th form, create all components of the given DIRECTORY(ies).\n\ >> -- >> 1.6.0.3.866.gc189b > > Just two ideas: > 1) I guess program_name variable should be used instead of "install" in > the first added sentence... although it is no-difference change on > almost every system and could be meant This install program" generally > and not just "This 'install' program".
I prefer not to say "This ginstall program...", and think the use of the generic "install" is actually desirable here. > 2 (heretical)) What about shipping ginstall (and ginstall.1) with > install/install.1 just as symlinks pointing there ... Then you will get > pointer to ginstall manpage even for man install and such change should > not break anything ... In report bugs section will be something like > "Report ginstall bugs to <[email protected]>" which could be more > clear for everyone ("ginstall" word is simply not "install" word and > could not cause confusion). You're right. That's heretical ;-) _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
