An 'interesting' problem when using the new vw7.6 Store rename semantics
on a repository that predates 7.6:
We have in our repository a package A with several historical versions,
later it was renamed to 'B' (7.4.1 time frame) and we continued using
both packages in our projects. This means that /both/ packages got
newer versions added over time.
We made B a prerequisite of A just after the rename.
In one of our build strategies we use 'load latest version with blessing
above x' for prerequisite resolution.
Now that 7.6 supports package renaming we get the into the situation
that when Store looks for the prerequisites of A it will find B to be
the declared prerequisite but it will also consider all the versions of
A (i.e. itself) as prerequisites of A (since it now considers renamed
packages as identical).
Note that it will consider *all* versions of A instead of just those
versions up to the rename. This throws Store into a loop loading A as a
prereq of A.
We hacked the DB and manually broke the 'trace' chain, so we could
proceed with development. We would prefer if Store could handle this
situation and consider versions of A up to the rename as being identical
to B - it should exclude versions of A created after the rename.
R
-
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
