Re: [Bashburn-info] Install.sh options
Brought to you by:
bashburn
From: Steven W. O. <st...@sy...> - 2008-09-29 17:23:47
|
On Monday, Sep 29th 2008 at 13:09 -0000, quoth Nick Warne: =>On Mon, 29 Sep 2008 13:05:20 -0400 (EDT) =>"Steven W. Orr" <st...@sy...> wrote: => =>> =>Well, I find it a bit brain dead if a user mistypes '--prefix' as =>> =>'-prefix' and it installs into a directory called 'refix'. =>> => =>> =>BTW, SVN is back up =>> =>> yabut your solution seems to imply that short options should be =>> constrained to uppercase (even if they *don't* take an argument). =>> Remember that creating options is not just a question of SVR4 =>> compatibility; it's also a question of following conventions to make =>> it more familiar. =>> =>> e.g., -h == help =>> -v == verbose =>> -V == Version info =>> -c == alternate configfile =>> -d == directory spec =>> -i == install =>> -l == long output =>> -n == don't do it but tell me what you want to do =>> -o == output =>> -q == query status returned =>> -R == recurse =>> -t == set a type =>> -u == uninstall =>> => =>OK, I understand. But there must be a way to stop it? Unless I am =>messing to much. I will have to try other install apps stuff to see :-D I dunno. If you really hate it, I suppose we could hardwire a check in to see if the arg to -p is refix and reject it unless the user also adds a -f option (or --force) to force it. ;-) -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steven W. Orr |