Hi

I was just thinking why using CVS because it seems to me really old and 
not really well design
(like loosing history), then cvs is good for file but what you would 
like to know is the changes or versions in terms of OO concepts like in 
Envy where we could know which method changed.

I have not a precise image of the complexity of a cvs stuff but this 
does not seems that big.

I was also thinking: does somebody thought of using a Store server to 
store Squeak code?
because we could reuse all their store code (even if it could be 
better).

Stef


On Friday, May 9, 2003, at 06:36 PM, Ivo Rössling wrote:

> Hi there!
>
> I'm a newbie on this list, so I might not know all the background 
> information...
> However - I am fortunately not a newbie in cvs anymore (both, using and
> administrating...) - so maybe I could be of any help in solving this 
> problem...
>
>> Is there some kind CVS savvy person with a bit of time that can tackle
>> this for us?
>>
> Shouldn't be a too big problem....
>
>> The older stuff needs removing and replacing with the new
>> tree; unless you are _very_ good indeed with CVS wizardry it is
>> understood that we will lose the history of the replaced files.
> Not necessarely... It depends on what exactly you wanna do...
> If you want to import an already somewhere else existing CVS repository
> (with the new tree), then you'll loose the history the respective tree 
> in the
> repository at SF...
> If you just want to import the latest version of the sources, than you 
> could
> take use of the "cvs import" command, which should be exactly what you
> are looking for: importing code from external sources...
> Applying it on an empty repository / directory take over the whole 
> directory
> structure 1:1 into the repository. Applying it on an already existing 
> repository
> instead would import the whole thing into the vendor branch (which is 
> 1.1.1
> in general).
> Then you have the choice to either merge the changes step by step into 
> the
> main trunk - or (what seems to me what you want to do here) to revert 
> local
> changes completely and return to the latest vendor release (, which 
> you just
> imported the step before)... The "cvs admin -b" command might help you 
> in
> the latter case...
>
>> I could probably attempt a basic attack but somebody that really 
>> knows what they're doing is so much more likely to get it right...
>>
> I've noticed that there're already at least two more or less 
> volunteers, so I
> don't want to interfere... - to many cooks just spoil the broth... ;-)
> However - if you need addtional help to handle this, just say a 
> word... :-)
>
> Cheers,
> Ivo.
>
> P.S.: If you finally intend to take use of the import command to 
> update the
> vendor branch, it is recommendable to use the same "vendor tag" but a
> different "release tag" to what you used during the first import - 
> which is
> "Squeak" as a vendor tag and "start" as a release tag, as I can see 
> from the
> repository at SF... This ensures that you'll log onto the same vendor 
> branch
> as at the first time...
>
>