Post AcDMEs3taB5h4DaNHM by colby@kosmos.social
 (DIR) More posts by colby@kosmos.social
 (DIR) Post #AcDMEVDKWvyICop5I8 by colby@kosmos.social
       2023-11-26T22:42:50Z
       
       0 likes, 0 repeats
       
       "Dependencies Belong in Version Control" <https://www.forrestthewoods.com/blog/dependencies-belong-in-version-control/>via @forrestthewoods
       
 (DIR) Post #AcDMEWKSNvGZfDAI2S by colby@kosmos.social
       2023-11-26T23:43:06Z
       
       0 likes, 0 repeats
       
       @simon re <https://news.ycombinator.com/item?id=38425594> what would be the point of having those dependencies in S3 rather than in the repo (or another repo), as you first described?  Seems needlessly disjoint.  (Let's assume for the moment that PyPI isn't as stable and reliable as we'd like.)
       
 (DIR) Post #AcDMEX1hn7rRpLOpRw by simon@fedi.simonwillison.net
       2023-11-27T00:00:24Z
       
       0 likes, 0 repeats
       
       @colby S3 feels like the cheapest most reliable place to keep backups of them, but honestly a separate repo would work fine too
       
 (DIR) Post #AcDMEs3taB5h4DaNHM by colby@kosmos.social
       2023-11-26T22:54:14Z
       
       0 likes, 0 repeats
       
       Boy did than story tank on HN.  It went from being one of the top submissions to being halfway down the page to not even being on the front page at all within an hour or so.
       
 (DIR) Post #AcDs0Ela59ibfp5L6G by colby@kosmos.social
       2023-11-27T05:56:46Z
       
       0 likes, 0 repeats
       
       @simon I've been spurred twice in the last week to comment about how Git's branching model means that the separate repos (one with deps and other cruft) don't even have to be disjoint.  I ended up scuttling both.Use sub-/superset repos.You're working on a project at foo-org/foo.  Your second, "full-fat" repo with all dependencies can just be a fork with the only difference being it also has a branch (or branches) deps get committed to.  This branch never gets merged/pushed to the main repo.