Andreas Raab wrote:
>>If you're filing out with DVS and you expect people to be able to 
>>update, you'll want to use #fileInPackageNamed: because of the diffs. 
>>Otherwise, if you delete a method it won't get deleted when the .st 
>>file gets filed in (the file-out of DVS doesn't include removals).
> 
> 
> I don't understand this. Can you please explain a) what an "old-style" SAR
> is and b) what removals have to do with it and c) what to do instead of
> using DVS?
> 
> And please, speak very slowly ;-)

I think there was an old version of the SAR builder that called the 
wrong method to do the DVS file in.

DVS fileouts don't include removals: they are quasi-declarative in that 
they describe a specific package state - when you file in with 
#fileInPackageNamed: in DVS, DVS compares the state of the package in 
the image with the state of the package in the file and does adds and 
removals as necessary to bring the image in line with the file.

If you file in using #fileIntoChangeSetNamed:fromStream:, you won't get 
removals performed because the fileout will simply be executed (and 
being essentially declarative, that is always additive).

As for what to use instead, we're trying to move to using Monticello 
instead.  You can load the Monticello CVS package as well and then you 
can use it basically just like DVS, except with the benefitsee changes 
between the image and a package on disk, a more robust model, etc. 
Monticello also happens to be where people are putting their effort at 
the moment so fixes and enhancements are way, way more likely than with DVS.

You can also choose to use the full versioning of Monticello, but that's 
an entirely new topic that I won't get into here (there are plenty of 
other email on it recently).

Cheers,

Julian


-- 
julian at beta4.com
Beta4 Productions (http://www.beta4.com)