At 10:34 AM 11/19/01 -0800, Chuck Esterbrook wrote:
>On Monday 19 November 2001 08:30 am, Geoff Talvola wrote:
> > Propagating stylesheets...
> > Traceback (most recent call last):
> >File "install.py", line 421, in ?
> > Installer().run(verbose=verbose)
> >File "install.py", line 55,
On Monday 19 November 2001 08:30 am, Geoff Talvola wrote:
> Propagating stylesheets...
> Traceback (most recent call last):
> File "install.py", line 421, in ?
> Installer().run(verbose=verbose)
> File "install.py", line 55, in run
> self.installDocs()
> File "install.py", line
On Monday 19 November 2001 07:58 am, Mike Orr wrote:
> I missed the connection between this and whatever the original
> problem was. However, it *is* true that it's inconvenient to
> upgrade Webware or do a CVS update on it because that creates
> conflicts in your configuration files. One strate
At 07:37 AM 11/19/01 -0800, Chuck Esterbrook wrote:
>On Friday 16 November 2001 08:05 am, Geoff Talvola wrote:
> > I feel that install.py shouldn't modify any files that are under source
> > control. I'm fine with it creating _new_ files however.
>
>I forget which files it modifies. Can you refre
On Mon, Nov 19, 2001 at 07:37:35AM -0800, Chuck Esterbrook wrote:
> On Friday 16 November 2001 08:05 am, Geoff Talvola wrote:
> > I feel that install.py shouldn't modify any files that are under source
> > control. ?I'm fine with it creating _new_ files however.
>
> I forget which files it modifi
On Friday 16 November 2001 08:05 am, Geoff Talvola wrote:
> I feel that install.py shouldn't modify any files that are under source
> control. I'm fine with it creating _new_ files however.
I forget which files it modifies. Can you refresh my memory?
I plan on adding an --expand-docs=no option
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
