I'm not sure I like the recent change that requires install.py to be run before you can use the AppServer.
I use Perforce for source control, and I have Webware checked into Perforce. Periodically I update my Perforce copy of Webware from Webware's CVS repository. Unlike CVS, Perforce uses a system where you must explicitly "check out" files in order to edit them. Otherwise, the files remain read-only in your filesystem. But "install.py" actually modifies files that are checked into CVS. This means that I can't run Webware from a Perforce workspace without checking out a bunch of files (to make them read-write) and running "install.py". Then I end up with a handful of checked out files that I never actually intend to check in. I used to be able to just run Webware directly out of a Perforce workspace without any such messing around. I feel that install.py shouldn't modify any files that are under source control. I'm fine with it creating _new_ files however. Either that or we shouldn't require running install.py. (In the meantime, I'll probably just fake it out by putting a "_installed" file into the Webware directory in Perforce.) -- - Geoff Talvola [EMAIL PROTECTED] _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
