Exactly.

Snapshotcello is meant to be used when you want to reproduce an image.

I believe the confusion in this discussion comes from Stephan referring to a snapshot as a means to define a dependency from other configurations. For that purpose it is not yet useful.

I think the problems starts when you put snapshots in a configurations:

> they mess the configuration up.

> they cannot be maintained: they only freeze the situation.

I remember trying to fix this problem, but I came to the conclusion that the design for snapshot cello is not sound.

I came to the conclusion that they solve a different problem than configurations and therefore the result should not be put in the configuration!

I suggest we fix snapshot cello and make it produce a separate class called: “SnapshotOf…” and puts the snapshots in here. The input is a configuration, so maybe it is easier to inherit this class from the configuration, or keep a different reference, but the original configuration should remain untouched, so it keeps working.

Diego

We CANNOT reproduce the versions we ship to clients and this DOOMED to failure.

Snapshotting is key and it was working.
Having development belssing for development is ok only if you can version versions when you want!
This is a basic principle to manage mess.
Else how can we maintain a product during a couple of years (Hakcing carefully a fucking image?)
I'm a software engineering not an handcraft. Tools should work.

Stef

On 26/6/14 13:02, Stephan Eggermont wrote:

Hi Stef,

What exactly are you trying to achieve here?

Adding more flattened snapshots to the ConfigurationOfMoose
is i.m.o. not a good idea. I've never found snapshotted
versions useable for development. Within a week there
were incompatible changes that break the snapshot version.

Snapshots can be a valuable artifact, and should be separate
from configurations.

Stephan