Re: [scons-devel] First split up of SConf.py

> If both Aap and SCons developers can update the files in this project,
> then we have a nice way to share file(s).  You can include the latest
> version in SCons, check for any problems, fix them and check in the
> corrected version.  When substantial enhancements are made you may chose
> to keep using an older version.
> 
> > I already have infrastructure in place for some of this (I'm maintaining
> > TestCmd.py as a separate project internally), so I'd volunteer some time
> > to set up things if we wanted to go this direction and no one else has
> > more cycles and is eager to do so.
> 
> Fine with me!

Okay, I'll go ahead with this in the next day or two.

> > Any other ways we might manage it?  Comments?
> 
> How about using Subversion for this?  It's getting to the quality level
> where it's reliable enough for actual use.  And this small project would
> be a nice way to find out if it indeed works better than CVS.  Just an
> idea.  It will be more work, but should give us experience with
> Subversion.  People not developing this project would simply download
> the file (Subversion allows downloading any file using a URL).

I'd actually really like to use Subversion, but my first thought for
all of the other management junk, of course, is to register it at
SourceForge, which uses CVS.  (The name Conftest is still available...!)
Is there a way that we could use Subversion for a SourceForge-hosted
project?  If not, do you have reliable server space to offer as a
central repository for checkins?

        --SK



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01