I wonder how this can get out of its current catch 22 situation where the main thing that makes it interesting is the easy access to a wide range of packages in a central repository, but having a wide range of packages available depends on having a wide range of people interested.
At the moment, their crates.io equivalent, cppget.org, has only 24 packages (mostly build2 itself and a few example packages), and it’s not clear if there’s any infrastructure for users to submit their own packages. They also face the additional issue that unlike cargo, build2 has come much later in the life of C++, so it probably needs a strategy to make existing, widely used, libraries available in the repository.
Yes, it can be used with a local repository, but at least for open source dependencies, the nice thing about cargo is that you tell it you want to depend on foo >= 1.0 and it does everything else for you. This experience is also very important for people who just want to try it out for the first time.
I wonder how this can get out of its current catch 22 situation where the main thing that makes it interesting is the easy access to a wide range of packages in a central repository, but having a wide range of packages available depends on having a wide range of people interested.
At the moment, their crates.io equivalent, cppget.org, has only 24 packages (mostly build2 itself and a few example packages), and it’s not clear if there’s any infrastructure for users to submit their own packages. They also face the additional issue that unlike cargo, build2 has come much later in the life of C++, so it probably needs a strategy to make existing, widely used, libraries available in the repository.
Yes, it can be used with a local repository, but at least for open source dependencies, the nice thing about cargo is that you tell it you want to depend on foo >= 1.0 and it does everything else for you. This experience is also very important for people who just want to try it out for the first time.