Paul Fultz II
Paul Fultz II
Support a null package source, this will allow meta-package recipes which combine multiple requirements. The question is what should this package be called. It should be something that cannot interfere...
If a requirements file is available from a recipe, then install requirements first before downloading the current package.
Specify build variants such as debug, release, shared, and static.
Right now, we use the filesystem, to store info about the name and its dependants. It might be better to use a db such as sqlite.
Perhaps the user could write: ``` somelib --when VAR=On ```
Cget was updated to install single files [here](https://github.com/pfultz2/cget/issues/46), so it would be useful for CMakeGet to support the same thing.