Re: [BuildStream] How to synchronize nested junctions



Hi Tristan,

    "BuildStream uses the junction element name as key to determine
     which junctions to merge. It is recommended that the name of a
     junction is set to the same as the name of the linked project."

I realize that this is really not an obvious thing to realize in
practice, maybe we need better messaging around this (and maybe there
are still edge cases around this which don't work perfectly and
conveniently ?).

Maybe even some enhancements are possible around here, I am skeptical
about having recursive junction lookups; when the end project wants to
address sub-sub project elements, there is already the option of
including a matching junction to the sub-sub project in the calling
project, using a matching junction element name.

Before considering further enhancements, I just wanted to point out the
current, existing solution for this.

I agree that we should try the existing solutions before considering
further enhancements, but I am not sure if we have any existing
solutions for the use-case that I mentioned. Having a junction
matching to the sub-sub-project is what we have now, but it requires
them to be kept in sync. Is there a trick I am missing here? Because I
don't see a way around keeping the two junctions in sync, without
enforcing that as an external process.

Cheers,
Chandan


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]