Ability to define a set of cci packages for local building

[rockdreamer]

As a maintainer of a medium sized set of packages for a company using Conan/Artifactory, I'd like to be able to use something like bincrafters/templates to build them.

Our current workflow allows rebuilding packages from cci on a set of profiles of interest and publish them on our internal server. I'd like to use bincrafters-package-tools to make this possible.

This is just an initial proposal: let's consider cci special and give it a folder called cci-recipes. For every package in cci that we're interested in, a yml file is added. For example, a cci-recipes/zlib.yml file could look like this.

---
versions:
  - 1.2.8
  - 1.2.11

A change in the file then triggers a rebuild.

Open Questions:

• How do we deal with changes in the cci packages?
• When a version is added, do we rebuild old versions? if not, how do we avoid rebuilding them?

[rockdreamer]

So I've been reading through code and I can see an alternative proposal being to add a recipes/zlib/config.yml file like the above and just add a cci: true line to it