From: Baruch E. <ba...@ev...> - 2001-07-31 13:32:13
Attachments:
password.diff
|
Back again. Attached is the updated patch to change the password upon installation. This time I added an option to disable prompting, which is usefull for packaging (debian .deb and RH .rpm). I added a -h option for help screen, and added a long version of the parameters as is customary in the current days unix world. Added two checks for IO errors, just for a saner fallback. Comments? -- Baruch Even http://baruch.ev-en.org/ |
From: Chuck E. <Chuck@StockAlerts.com> - 2001-07-31 14:11:44
|
At 04:35 PM 7/31/2001 +0300, Baruch Even wrote: >Back again. > >Attached is the updated patch to change the password upon installation. > >This time I added an option to disable prompting, which is usefull for >packaging (debian .deb and RH .rpm). > >I added a -h option for help screen, and added a long version of the >parameters as is customary in the current days unix world. > >Added two checks for IO errors, just for a saner fallback. > >Comments? Looks good overall. I might axe 'n' as a short cut for "no-password-prompt" because it doesn't distinguish well against other future args like "no-doc-generation". Also, any opinions on whether we go with: --no-this-or-that or with: --this-or-that=0 (or 1) (I'd also accept 'no' for 0 and 'yes' for 1.) ? Should we allow the password to be passed on the command line? python install.py --set-password=sk3oi9cn -Chuck |
From: Chuck E. <Chuck@StockAlerts.com> - 2001-07-31 15:34:50
|
At 06:23 PM 7/31/2001 +0300, Baruch Even wrote: >I don't mind removing 'n' it was just my thought to add a shortcut, I'm >not attached to it. > >I preferred the --no version due to simpler coding, this is after all >intended to be used by some packaging script and a human could also cope >with it. Simpler coding on the inside or outside? On the outside, it seems that it's just as easy to say: python install.py --expand-docs=no as: python install.py --no-doc-expansion > > Should we allow the password to be passed on the command line? > > > > python install.py --set-password=sk3oi9cn > >I don't think we would want that. It's opening the door for unwanted >behaviour (like having a fixed password on packaged install). Well it enables scripting. For example, someone could write an "install my app and all its dependencies" script for their intranet server which would download and install Python, Webware, MySQLdb, etc. with no intervention required. -Chuck |