Some plans for scmproj

[Alexander Belchenko]

I will comment other questions a bit later, right now some clarification about snapshot and deleted 
component.

Michael Gliwinski пишет:
> On Wednesday 09 December 2009 14:12:25 Alexander Belchenko wrote:

>>> I don't know if I understand how snapshots should work, but if they
>>> record revision ids of component branches in a config file in project
>>> control branch, wouldn't you have problems e.g. when a component is
>>> removed from project.cfg in control branch?
>> Snapshot will be stored separately of project config, and will be
>> updated often enough. So, no. There should not be a problem if component
>> will be removed. Snapshot file will be updated based on current config.
> 
> Note that I haven't yet read much doc/code regarding snapshots yet so I may be 
> talking nonsense here.  I plan to catch-up this weekend.
> 
> What I meant is a scenario like that:
> 
> You have a control branch at rev 1 where project.cfg defines components A and 
> B.
> 
> 1. create snapshot: records components' revisions
> 2. do some more changes to the control branch, say up to rev 5
> 3. commit revision 6 to control branch which removes component B from 
> project.cfg
> 4. now try to restore snapshot created in 1.  basically this snapshot refers 
> to component B which doesn't exist in rev 6 of the control branch

You can't "restore" snapshot actually. If you get copy of the project from revision 6 of control 
branch the project config will clearly shows that there is no component B, therefore no data for 
component B will be present in snapshot. If you get copy of project from revision 5 or before when 
component B still present, you'll get full project (A+B) with their actual tips as they saved in 
snapshot.

Anyway, project config is main data, snapshot is supplementary data.

Is it clearer now?