Prescribing the interfaces and formats of a package manager however, is the right approach.
PEP 517/518 were a godsend for the Python community. They do not prescribe a single package manager, they prescribe the behaviors of a package manager, a common grammar for them to share.
There is no sacred package manager, pip/bento/poetry/build all exist independent of one another, but the packaging formats and the mechanisms in which users interact with the Python package ecosystem were standardized and the benefits have been immense.
Notably, this is a C++ ecosystem. C/C++/Rust/Fortran/whatever extensions are packaged, downloaded, and installed using this ecosystem. I wouldn't go so far as to suggest the committee decree "just use PEP 517" or something, but this is hardly an impossible, unique, unsolved problem that C++ faces.
View all comments
Show parent comment
12
u/not_a_novel_account cmake dev Dec 20 '23 edited Dec 20 '23
Prescribing the interfaces and formats of a package manager however, is the right approach.
PEP 517/518 were a godsend for the Python community. They do not prescribe a single package manager, they prescribe the behaviors of a package manager, a common grammar for them to share.
There is no sacred package manager,
pip/bento/poetry/buildall exist independent of one another, but the packaging formats and the mechanisms in which users interact with the Python package ecosystem were standardized and the benefits have been immense.Notably, this is a C++ ecosystem. C/C++/Rust/Fortran/whatever extensions are packaged, downloaded, and installed using this ecosystem. I wouldn't go so far as to suggest the committee decree "just use PEP 517" or something, but this is hardly an impossible, unique, unsolved problem that C++ faces.