add new build format cep

[wolfv]

This is a mashup of the boa / rattler-build and conda-build documentation for the new recipe spec.

I am not sure in how far we want to spec out things here since there are two speccable things:

• allowed inputs
• expected behavior

This is already a bit of both. What's missing is for example a section on run_exports, including the ignore_run_exports_from and ignore_run_exports. However, when specifying these inputs, we probably also want to specify the behavior a little bit?

I also need to expand more on the expected behavior of outputs and how "merging" works with the top-level recipe.

Todo:

• document all build keys
• spec out variant config files and variant evaluation
• document all available selector variables (unix, win, ...)?
• figure out if documenting package hash computation is part of this spec or not
• finish jinja function docs incl. all allowed inputs
• think more about cmp function

[dhirschfeld]

Just mentioning one of my personal bugbears; if we're making changes, I think specifying test dependencies under requirements/test makes a lot more sense than special-casing them under their own top-level heading.
e.g.

requirements:
  build:
    - "{{ compiler('c') }}"
    - sel(linux): "{{ cdt('xorg-x11-proto-devel') }}"
  host:
    - python
  run:
    - python
    - sel(py26): argparse
    - six >=1.8.0
  run_constrained:
    - optional-subpackage =={{ version }}
  test:
    - nose

[jaimergp]

Suggested change

	Requirements section
	--------------------
	## Requirements section

[jaimergp]

Suggested change

	Outputs section
	---------------
	## Outputs section

[jaimergp]

To clarify, this behaves like any([item for item in list]) right?

[jaimergp]

Can selectors be nested? Should they?

source:
  - sel(not win):
      url: http://path/to/unix/source
      sel(py3k):
        url: http://path/to/python3/bindings/linux/only
  - sel(win):
      url: http://path/to/windows/source
      sel(py3k):
        url: http://path/to/python3/bindings/windows/only

[wolfv]

I've decided to split the proposal up into multiple sub-proposals, the first one is

1. About the new YAML format incl. selectors, allowed Jinja, ... A new YAML based format for "conda-build" files #54
2. The allowed keys / values in the new format (excluding outputs)
3. Specify how variant computation is working
4. The new specification for how outputs should behave
5. The new test magic

If someone thinks that we should split into more parts let me know! :)

[tdejager]

Suggested change

	These are moved to the appropriate Python-version specific locations when installing.
	These can be moved to the appropriate Python-version specific locations when installing.

As this spec does not dictate anything about installing right?

[wolfv]

Closing because we've split this CEP into multiple smaller ones :)