On Sun, 10 Dec 2000, Mark Murphy wrote:
> > If this creature is only going to run on Windows, I don't see any
> > problem with using Visual Basic. Maybe Branko will have an issue with
> > it because of the build system, but that's the only problem I can see.
>
> There's no question building VB apps typically doesn't follow the normal make system.
>
> There *is* some way to compile a VB app outside the IDE -- the VB Package
> Wizard can recompile a project. But I don't know if that interface is
> documented, or whether we'd want to use it to somehow build WinSVN
> as part of the overall build system.
>
> Greg Stein's comment on a separate CVS tree would also suggest that
> clients use independent build processes, appropriate for the
> technology used to build them (e.g., VB IDE for WinSVN, javac
> for a Java client, nothing at all for a Tcl/Tk client).
> Ideas?
>
> Mark Murphy
> mmurphy@collab.net
The build process for a GUI should be separate from building
SVN. Sure, it might seem like a good idea to have the
user run "./configure ; make install" to get everything,
but I doubt that will work in real life. Why would
someone that wanted to use the SVN cmd line client
care about getting GUI's to build?
Mark's comment about doing it in Tcl/Tk makes a
lot of sense to me. A Tcl/Tk client for SVN would
run on most/all Unix systems, Windows, and Mac OS.
Just my 2 cents
Mo DeJong
Red Hat Inc
Received on Sat Oct 21 14:36:16 2006