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.

they mess the configuration up. they cannot be maintained: they only freeze the situation.

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

Yes this is a good idea. Snapshotcello is just useful when we want to package/archive something for a client if all the packages of Moose are not released/versionned. I think that the real solution is to make sure that we can use versionner. We started to do some experiences and this is really promising. We can use the baseline when developing and when releasing freeze all the versions to versions. Christophe was looking at the problem with us and can address some problems. In addition, we could have a ci job that check that there are newer package in the repository than in the loaded one. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev