Re: [p2-dev] duplicate IUs

[Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>]

The potential problem with duplicates in a composite repository is that the user may be shown the same IU twice. This could be confusing, especially since composite repositories appear to the user as a single repository. However, the UI model elements today use a HashSet over the query results to perform some post-processing, so I don't think this will happen in practice in the SDK UI.

I do find it odd that the behavior will be different depending on what kind of query it is. That is, duplicates within a queryable would be filtered out, but any query that involves multiple queryables would not eliminate duplicates. Is there a reason for this difference or is it simply the result of the current implementation? The inconsistency bugs me a little.

susan

Ian Bull ---03/31/2010 10:56:01 AM---I was fixing some bugs in my repository analysis tool and testing it against the Galileo repository. I noticed that we had dupl

Ian Bull <irbull@xxxxxxxxxxxxxxxxx> Sent by: p2-dev-bounces@xxxxxxxxxxx 03/31/2010 10:55 AM Please respond to P2 developer discussions

To: P2 developer discussions <p2-dev@xxxxxxxxxxx> cc: Subject: [p2-dev] duplicate IUs

I was fixing some bugs in my repository analysis tool and testing it against the Galileo repository. I noticed that we had duplicate IUs in the repo, so I took a closer look.  Since galileo is a composite repo (pointing to SR1 and SR2), there are duplicates between these two child repos.  Currently the query mechanism (if you use the iterator) is setup to append the two sets, but not necessarily setify the results.  Thomas brought this up a while back and I didn't think much of it.  Does anyone think this will cause a problem?

cheers,
ian

-- 
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev