Re: Build managment with Delta-V
Jim Whitehead (ejw@ics.uci.edu)
Wed, 28 Jul 1999 21:49:22 -0700
From: Jim Whitehead <ejw@ics.uci.edu>
To: Damon Poole <damon@ede.com>, ietf-dav-versioning@w3.org
Date: Wed, 28 Jul 1999 21:49:22 -0700
Message-ID: <NDBBIKLAGLCOPGKGADOJAEFACCAA.ejw@ics.uci.edu>
In-Reply-To: <199907290332.XAA11119@roxie.ede.com>
Subject: RE: Build managment with Delta-V
Damon Poole writes:
> I suggest a small change. Substitute 'derived object' for 'Build' .
>
> There are many indications that CM of software projects will play
> a smaller and smaller role in the growth of CM.
>
> Many tools other than compilers will be used (are being used) to create
> derived objects.
Excellent point! Having myself used such tools, I'll self-award myself 20
demerits...
> If Delta-V has generic support for sources being manipulated by tools
> to create derived objects where the tools and objects may or may not be
> local, I think it will have broader applicability.
>
> I re-read your post a couple of times and wasn't sure if you were
> just looking
> for usage patterns or also suggesting that Delta-V should include support
> for derived objects?
Well, I was mostly looking for proposed usage patterns, but I'm also
wondering whether some usage patterns would be easier to support with some
standard protocol support. For example, if links were used to associate
derived objects with their sources, a small set of standard link types might
be handy.
- Jim