On Friday 01 November 2002 09:51, you wrote: > On Fri, 1 Nov 2002, Stephan Diehl wrote: > > On Thursday 31 October 2002 20:42, you wrote: > > > So I'd like to expand MakeAppWorkDir.py to do these two things when you > > > run it (i.e., you'd pass your main context name in as an command-line > > > argument to MakeAppWorkDir, and it adds a lib directory to the workdir > > > and the Python path). Do people have other things they'd like to see > > > added? > > > > It would be nice to have an init start script created as well. > > Abstract: > > Generating a correct startup script for every platform isn't easy and > should only be an option, with the default to not install a startup > script. > > More verbose: > > If you install a startup script, please consider that such a script > may have to vary across (Unix-style) operating systems. Sure, if it > works it's convenient, but if MakeAppWorkDir would put a wrong kind of > startup script or put it in the wrong path, that's not so fine. > Additionally, some people may have made their own scripts and > MakeAppWorkDir should care to not overwrite it (which may be a problem > if the existent startup script has another name than expected by > MakeAppWorkDir). > > Stefan
The wording of my suggestion was a little short :-) I didn't want to suggest to install the script automatically. The webware distribution already has a somewhat generic start script. It would be helpfull (at least I think) to have such a script with the path to the AppWorkDir filled in, maybe some suggestion of a AppWorkDir specific logfile, etc. ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
