unison formal review

[Jesse Keating]

On Sep 29, 2011, at 12:50 PM, Dominik 'Rathann' Mierzejewski wrote:
> 
> One solution would be to make per-version subpackages conditional via macros
> and build only the one that has been updated. 
> 
> Example: we have unison-2.9-1 package which produces
> unison-2.9-1
> unison28-2.8-2
> unison21-2.1-5
> 
> We want to update unison28, so the next build of unison-2.9-2 produces only:
> unison28-2.8.1-1
> 
> What do you think?

The build system would not return a sub package from an older build when you go to compose the tree.  Instead you'd only get the sub packages that are in the latest build.  The old ones will disappear.

- jlk