Michael Rueger wrote:

>> CVS handles versioning based on source code files, not classes or
methods.
>> This works reasonably well if your development environment just
consists
>> of separate source code files, e.g. C++.  Typically you might have all
of

>One way a Web based CVS would help immediately is to store all the
>contributions and change sets there.
>Most of the Squeak packages/goodies even updates come as a single change
>set file and could be stored and versioned using CVS.

You made a good point here but I don't like the Idea of having
a number of different change set files in different versions.
The problem is that you don't see at a first glance which 
change file affects which classes. Furthermore the classes in
the changes files don't carry version information so if you find
two chage sets which affect the same class you don't know if you 
can load them both and in which order.

>> So, I tend to think some sort of source code database (image?), similar
to
>> ENVY, would be better.  (Of course, ENVY does have some problems with
its

>I agree with you in regards to a local (possibly team) environment.

And this is what I was heading for. I thought of an ENVY-like server in
a LAN or even WAN written completely in Squeak that manages one change 
file (with some additional information and pointering) and thus replaces
the image and changes files of all its clients.

Squeak on
Torge


-- 
Sent through Global Message Exchange - http://www.gmx.net