tee3 / boost-build-package-manager

A Boost.Build module for managing packages.

Hi there 👋

boost-build-package-manager's Issues

Commands execute immediately in all cases.

Some commands should probably be run no matter what, but others should not be.

For example, running the vcs-git tests with -n results in actual git-clone running. This is counter-intuitive behavior when the user has asked for only the commands to be printed.

This probably just means that we need to split things into targets and actions, but I haven't figured out how to do that clearly yet.

Some tests require tags on this repository to complete successfully

This should take care of itself once this project matures a little, but the test is actually a little sloppy in that it requires something to be true that isn't.

A potential workaround is to add a temporary tag when running the tests or just make an arbitrary tag in the repository to satisfy the requirements.

Tests rely on the hosting service to provide git, svn, and archives.

The tests are relatively clever in that they are all run on the same data if the hosting service provides the data for the projects via git, svn, and archive. In this case, the hosting service is GitHub and does provide all these.

However, adding new VCS systems will likely break this requirement and a better approach will be required at that time.