IRC logs for #buildstream for Sunday, 2020-06-14

*** hasebastian has joined #buildstream05:06
*** tristan has quit IRC05:15
*** hasebastian has quit IRC05:28
*** tristan has joined #buildstream06:28
*** ChanServ sets mode: +o tristan06:28
tristanSo links work perfectly now, but overrides are another tricky thing06:43
tristanIn order to preserve the "duplicated" relationship of a project and it's subproject (or subsubproject), when the duplicated subproject in question is overridden, we need to translate real junction paths into original project paths (pre-override)06:46
tristanjuergbi, Do you think it makes sense to do this ?06:46
tristanIf I override a subsubproject which is either internal or duplicated in the subproject I junction, should the internal/duplicated relationship be preserved ? or should I be forced to re-duplicate it or re-mark it as internal ?06:47
juergbiotoh I'd say internal should definitely be preserved06:48
tristanEven if I override it ?06:48
tristanHmmm06:49
juergbiyes, imo 'internal' is mostly between a project and its junction06:49
tristanIf I override it with a local junction, it also technically becomes a junction in my project06:49
juergbiit means that those subproject elements are not exposed06:49
juergbiin such a case 'internal' should be mostly irrelevant as you're essentially manually deduplicating06:51
tristanWell, I'm telling the subproject to use a more up to date version of it's internal project or smth, maybe06:52
juergbiyes. ideally, if that toplevel junction is also used directly and the toplevel project has another junction to the same subproject, we would still get a conflict06:52
juergbihowever, this may be tricky06:52
tristanNo I don't think so06:54
tristanWhen you override a subproject there is still only one project06:54
tristanOnly the search paths to reach it are changed, reversing that is indeed tricky06:55
juergbithe override itself is fine, of course06:55
tristanbecause there are an infinite number of overrides which can be traversed to reach an internal subproject06:55
tristanit may mean a try/search approach for each possibly way to reach a real path, finding every possible referrer to a project06:56
tristans/possibly/possible06:56
tristanHmmm06:57
juergbisorry, have to go07:01
tristanyeah07:01
tristanI'll see if I can wrangle up some kind of path translation easier than that07:01
tristanwithout it being expensive07:01
*** tristan has quit IRC07:05
*** hasebastian has joined #buildstream07:09
*** coldtom has quit IRC07:41
*** hasebastian has quit IRC07:43
*** hasebastian has joined #buildstream09:00
*** hasebastian has quit IRC09:14
*** coldtom has joined #buildstream10:32
*** coldtom has quit IRC10:47
*** coldtom has joined #buildstream10:47
*** tristan has joined #buildstream12:26
*** ChanServ sets mode: +o tristan12:26
tristanjuergbi, I've backported some cleanup/refactor to the top of my branch and made a separate MR: https://gitlab.com/BuildStream/buildstream/-/merge_requests/196413:42
tristanNo hurry, I'll ping you or Ben tomorrow13:43
tristanif you happen to feel like checking it out... I'm rebasing everything on that, because having it in the middle of my branch would have been madness to review13:43
tristangah14:27
tristandamn internal tests poking around at the ever changing insides :-S14:27
tristanhow many do we have left to refactor out of there I wonder...14:27

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!