#general
- w
witty-crayon-22786
10/09/2015, 6:10 PMhm, would be easy to do automatically at generation time though, right? - e
enough-analyst-54434
10/09/2015, 6:10 PMno - w
witty-crayon-22786
10/09/2015, 6:10 PMoh =/ - e
enough-analyst-54434
10/09/2015, 6:10 PMgo does not have versions at all - e
enough-analyst-54434
10/09/2015, 6:10 PMyou;d need to learn github, ... etc - e
enough-analyst-54434
10/09/2015, 6:10 PMscrape "versions" - e
enough-analyst-54434
10/09/2015, 6:10 PMand then do I don't know what - w
witty-crayon-22786
10/09/2015, 6:11 PMgo_remote_library has a
argument it mixes in, no?rev - e
enough-analyst-54434
10/09/2015, 6:11 PMuser supplied - w
witty-crayon-22786
10/09/2015, 6:11 PMbut yea, what you do with it is different for each type of url. - e
enough-analyst-54434
10/09/2015, 6:11 PMyes - w
witty-crayon-22786
10/09/2015, 6:12 PManyway... the skeleton is similar. the npm case would be easier from the perspective of shrinkwrapping - e
enough-analyst-54434
10/09/2015, 6:14 PMMy understanding of shrinkwrap is it == pip freeze, gemlock, etc - just use the trabsitive resolver - let it decide however, then write down the solution in a file and use that file instead with all exact soluved revisions - right r wrong! - from there forward - e
enough-analyst-54434
10/09/2015, 6:14 PMBasically believe the human to bless the lock file - e
enough-analyst-54434
10/09/2015, 6:15 PMIOW - this is a strategy pants could implement generically on top of any resolver for any lang - e
enough-analyst-54434
10/09/2015, 6:16 PMFor the go parallel - its like replacing all the human-forced-lookup-of-rev with an automated resolver - b
bright-dinner-81701
10/09/2015, 6:17 PMso - b
bright-dinner-81701
10/09/2015, 6:17 PMthe problem we’ve hit is that there is basically no way to generate node_modules dir recursively bottom-up from known packages of 3rd party modules with their dependencies - b
bright-dinner-81701
10/09/2015, 6:17 PMdedupe is worse than we thought - b
bright-dinner-81701
10/09/2015, 6:17 PMit goes to network and tries to download in NPM 2 - b
bright-dinner-81701
10/09/2015, 6:18 PMand NPM 3 flattens the tree for even an isolated install of a module, so there isnt really a canonical directory for the module even in the case of an isolated install - w
witty-crayon-22786
10/09/2015, 6:19 PM@enough-analyst-54434: it's also the same as foursquare's resolver, iirc - e
enough-analyst-54434
10/09/2015, 6:19 PM~yes - that's what I understand as well - w
witty-crayon-22786
10/09/2015, 6:19 PM(except you only declare enough to freeze the resolution) - b
bright-dinner-81701
10/09/2015, 6:19 PM(and i tried to fake it by downloading the sources and installing, and then npm installing, and npm 3’s dedupe exploded with errors on the output although it did actually produce a working result) - b
bright-dinner-81701
10/09/2015, 6:19 PManyway - b
bright-dinner-81701
10/09/2015, 6:20 PMyeah shrinkwrap is really dumb - just look at an existing node_modules directory, and produce a JSON file describing exactly the tree and versions - b
bright-dinner-81701
10/09/2015, 6:20 PMthen NPM install will follow exactly that in the future instead of its crazy install algo - e
enough-analyst-54434
10/09/2015, 6:20 PMthat basic dumb approach seems generally the most sane thing you can do with a transitive resolver/solver - b
bright-dinner-81701
10/09/2015, 6:20 PMok