title: Separate the dependency list ( requirements) from conanfile.py
body: <p>We are planning to set up conan repositories for our C++ codes. We want to expose only the list of dependencies ( lib/version@user/channel) to the developers, not the logic we put in conanfile.py We are planning so, because we are creating a wrapper around conan which will have several logic and checks. This wrapper will be exposed to the users. They do not need to know the detailed logic and build steps.</p>
  
  <p>Is there a way to implement the requirements ( dependency list ) outside conanfile.py, and make the list available to the users, so that they can choose which version of the library they want to use - something similar ( not same, though ) to pom.xml in maven world ?</p>