njlr

This is quite an old issue, but I think the experience still could be better. Yes, GitHub packages are identified by a GitHub URL. For example: ``` buckaroo add github.com/buckaroo-pm/[email protected]...

Documentation is here: https://github.com/LoopPerfect/buckaroo/wiki/Version-Constraints-DSL

The projects under the [buckaroo-pm user](https://github.com/buckaroo-pm/) are forks we maintain that have `buckaroo.toml` and `BUCK` files added. To answer your questions: 1. We haven't added a `buckaroo.toml` file for `2.4.2`...

BTW, you can always fork Catch yourself and add the appropriate files. Once you've done that, it would be something like: ``` buckaroo add github.com/joeflack4/catch2 ```

This should work now: ```bash buckaroo add github.com/buckaroo-pm/[email protected] ```

There is a guide to getting the tools / dev environment setup here: https://github.com/LoopPerfect/buckaroo/blob/master/CONTRIBUTING.md Contributions are always welcome!

Once we have tags on dependencies, the behaviour of `buckaroo_deps()` should change to return all deps that do not have any tags. We would introduce a new function for returning...

Hi @iwatakeshi, thanks for the response! Our initial idea was exactly as you describe, with `os` and `dev` as built-in concepts. We came up with two issues with this approach....

Given that the build scripts are written in Python (well, a Python variant called [Skylark](https://buckbuild.com/concept/skylark.html)), a `filter` function is definitely possible. We can also have named arguments as you suggest...

Discussed here: https://github.com/LoopPerfect/buckaroo/issues/323#issuecomment-497363610