Re: Dual cache key calculation and build planning modes

[Paul Sherwood <paul sherwood codethink co uk>]

On 2017-07-06 11:03, Tristan Van Berkom wrote:
> On Thu, 2017-07-06 at 07:15 +0100, Paul Sherwood wrote:
> > Hi Tristan,
> > On 2017-07-05 10:05, Tristan Van Berkom wrote:
> > >
> > > Premise
> > > ~~~~~~~
> > > The premise is simply that every element has 2 cache keys generated at
> > > all times.
> >
> > I haven't had chance to follow all of the detail here, but isn't your 
> > 'weak' key just a hash of a subset of the same factors in for your 
> > 'strong' key?
> >
> > In which case, would it be simpler and better to have one key which 
> > combines both?
> >
> > foo.<hash(weak-factors)>.<hash(strong-factors - weak-factors)>
> >
> > Then tooling can decide whether it cares about the whole key or just 
> > the 
> > 'weak' part?
>
> Interesting idea, but I'm not sure what it would add.

If you have two keys, you always end up with two artifacts? 
Foo.weak.strong is one artifact that can be consumed for all use-cases.