Re: [b3] Cumulative aggregation

[David M Williams <david_williams@xxxxxxxxxx>]

As far as I know, this is exactly the way
it will work if you never "CLEAN" your build output location.


You might ask on the eclipse.b3 newsgroup/forum
... I'm don't think many follow this "users lists" and that news
group is where I ask all my "user questions" :) and get pretty
good responses and response times. 

I'm sure you are aware of all the additional
issues this may raise: 
 Sometimes you might _have_ to
remove something (say, if its illegal, or contains an especially dangerous
bug), 
 Whether or not someone "gets
the same thing" depends on features specifying exact versions for
other features they include. 
 It depends on stuff being added
having unique version/qualifiers if the content has changed. For example,
if someone submits something unsigned, gets added to your master repo,
and then later wants to add a signed version (with same id and qualifier)
the aggregator will think it already has it so won't replace it, as far
as I know). 
 Etc. 

HTH





From:      
 Pascal Rapicault <pascal.rapicault@xxxxxxxxxxxx>
To:      
 "b3@xxxxxxxxxxx"
<b3@xxxxxxxxxxx>, 
Date:      
 03/11/2013 12:30 PM
Subject:    
   [b3] Cumulative
aggregation
Sent by:    
   b3-bounces@xxxxxxxxxxx

---

Hi
 
I would like to know if it possible for
the aggregation to keep accumulating content in the final repository rather
than just pick the most recent version.
The situation I have is as follow, I aggregate
content from an external update site and I want to make sure that for each
run of the aggregator the most recent (and valid) version is added to the
aggregate but the previous version retained because my users may still
need those.
 
Thanks,
 
Pascal_______________________________________________
b3 mailing list
b3@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/b3