[RFC] fusion packages

[timotheecour]

links

• D20200421T170935
• RFC: chef, stable package manager based on nimble+homebrew · Issue #117 · timotheecour/Nim
• was being discussed here: https://irclogs.nim-lang.org/21-04-2020.html#13:48:12
• https://github.com/nim-lang/graveyard
• Developing Nim's stdlib and a Nim distribution · Issue #173 · nim-lang/RFCs : Developing Nim's stdlib and a Nim distribution · Issue #173 · nim-lang/RFCs
• nimterop/wrappers : nimterop/wrappers
• move tinyc to a separate repo and allow installing external dependencency (eg tinyc) from koch / library code by timotheecour · Pull Request #13850 · nim-lang/Nim

discussion

• we still need to use independent git histories for different packages, otherwise too slow to improve them
• maybe use git submodules?
• use homebrew's model?
• is it enough to add more features to important_packages?
• incentives matter; maybe ppl prefer more ownership of their pet package
• what helps would be common tooling so users don't have to reinvent wheel, eg: automate CI etc
• issue reporting would be a mess if using a monorepo

other langs

see boost: https://www.boost.org/doc/libs/1_61_0/doc/html/metaparse/versioning.html

Future versions of the library may provide other namespaces (eg. v2). The header files in <boost/metaparse/...> provide the latest version of the library. To always get version v1, one should use header files in <boost/metaparse/v1/...>.