[15:12:50 CDT(-0500)] <yura> so Bosmon we didnt finish talking abotu the dependency structure for platform dependant stuff

[15:13:11 CDT(-0500)] <Bosmon> Right

[15:13:11 CDT(-0500)] <yura> having univeral and linux as siblings still does not solve me problem

[15:13:36 CDT(-0500)] <yura> i need linux to be in node_modules on some level relative to flowManager

[15:13:39 CDT(-0500)] <Bosmon> What do you think about the idea of arranging checkout geometry using scripts, rather than submodules?

[15:13:42 CDT(-0500)] <yura> and other univeral components

[15:14:09 CDT(-0500)] <yura> yes it 's fine having them setup through scripts

[15:14:19 CDT(-0500)] <yura> but what is the structure taht we are agreeing on

[15:14:26 CDT(-0500)] <Bosmon> I think we decided that universal and linux wouldn't be siblings directly, since the whole of "universal" would need to appear in the node_modules directory?

[15:15:15 CDT(-0500)] <yura> no the other way around

[15:15:34 CDT(-0500)] <yura> universal has the executables

[15:15:50 CDT(-0500)] <yura> platform specific stuff needs to be resolvable against it

[15:26:32 CDT(-0500)] <Bosmon> AAAH

[15:26:36 CDT(-0500)] <Bosmon> Now I see

[15:27:54 CDT(-0500)] <Bosmon> Ok, so, platform-specific stuff appears in node_modules directory sibling to universal

[15:30:23 CDT(-0500)] <Bosmon> yura

[15:35:11 CDT(-0500)] <yura> well we dont have it yet

[15:35:27 CDT(-0500)] <yura> but it cant be in node_modules of sibling since node will not look in there

[15:36:38 CDT(-0500)] <Bosmon> I mean, the node directory which is a sibling - not the one belonging to the sibling

Browser not supported