{"action":"created","issue":{"url":"https://api.github.com/repos/conda/conda/issues/3017","repository_url":"https://api.github.com/repos/conda/conda","labels_url":"https://api.github.com/repos/conda/conda/issues/3017/labels{/name}","comments_url":"https://api.github.com/repos/conda/conda/issues/3017/comments","events_url":"https://api.github.com/repos/conda/conda/issues/3017/events","html_url":"https://github.com/conda/conda/issues/3017","id":164572250,"number":3017,"title":"Too many files to create an environment","user":{"login":"srossross","id":741611,"avatar_url":"https://avatars.githubusercontent.com/u/741611?v=3","gravatar_id":"","url":"https://api.github.com/users/srossross","html_url":"https://github.com/srossross","followers_url":"https://api.github.com/users/srossross/followers","following_url":"https://api.github.com/users/srossross/following{/other_user}","gists_url":"https://api.github.com/users/srossross/gists{/gist_id}","starred_url":"https://api.github.com/users/srossross/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/srossross/subscriptions","organizations_url":"https://api.github.com/users/srossross/orgs","repos_url":"https://api.github.com/users/srossross/repos","events_url":"https://api.github.com/users/srossross/events{/privacy}","received_events_url":"https://api.github.com/users/srossross/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-07-08T16:54:02Z","updated_at":"2016-07-12T22:12:52Z","closed_at":null,"body":"# Problem Statement\r\n\r\n## Too many files\r\n\r\nConda and anaconda have a growing number of files that can be used for different purposes, but achieve the basic functionality of creating or specifying an environment. \r\n\r\nSome formats add to this core, but they all share the same base. Yet each does this in a different way from the next.\r\n\r\n| Command |  Instals packages  | Channel support | pip support | project support | platform specificity | different requirement syntax | \r\n| ------------- | ------------- | ------------- | ------------- | ------------- | ------------- | ------------- |\r\n| `command line` | ✅  | ✅  | ✅  | ✅  | ⛔  | -  |\r\n| [`requirements.txt`](http://conda.pydata.org/docs/using/envs.html#build-identical-conda-environments) | ✅  | ⛔  | ⛔  | ⛔  | ⛔  | -  |\r\n| [`environment.yaml`](http://conda.pydata.org/docs/using/envs.html#use-environment-from-file) | ✅  | ✅  | ✅  | ⛔  | ⛔  | -  |\r\n| [`project.yaml | kapsel.yaml`](https://github.com/Anaconda-Platform/anaconda-project/blob/conda-kapsel-staging/kapsel-config.rst) | ✅  | ✅  | ✅  | ✅  | ⛔  | -  |\r\n| [`constructor.yaml`](https://github.com/conda/constructor/blob/master/CONSTRUCT.md) | ✅ | ✅  | ⛔  | ⛔  | ⛔  | -  |\r\n| [`cas-installer.yaml`](https://docs.continuum.io/anaconda-repository/cli-cas-installer#cas-installer) | ✅ | ✅  | ⛔  | ⛔  | ⛔  | -  |\r\n| [`meta.yaml`](http://conda.pydata.org/docs/building/meta-yaml.html) | ✅  | ⛔  | ⛔  | ⛔  | ✅  | 💀   |\r\n\r\n### Notes\r\n\r\n * [`meta.yaml`](http://conda.pydata.org/docs/building/meta-yaml.html)\r\n   * ✅ can use requirements.txt if found\r\n\r\n# Possible Solutions\r\n\r\n### Lets standardize. \r\n\r\nAs we move forward we should think about how adding new file formats and definitions affects the conda ecosystem. Are we going to have an ever growing list of file formats? \r\n\r\n * Should we deprecate a few in a planned and controlled way?\r\n * Should we standardize so that the core functionality is the same across all files? And the files can be written in the same way with the same syntax?\r\n * Should we define a base file `quiz-blag.yaml` that all tools look for to create their environment (just like meta.yaml uses requirements.txt if it exists)?\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/conda/conda/issues/comments/232197972","html_url":"https://github.com/conda/conda/issues/3017#issuecomment-232197972","issue_url":"https://api.github.com/repos/conda/conda/issues/3017","id":232197972,"user":{"login":"jakirkham","id":3019665,"avatar_url":"https://avatars.githubusercontent.com/u/3019665?v=3","gravatar_id":"","url":"https://api.github.com/users/jakirkham","html_url":"https://github.com/jakirkham","followers_url":"https://api.github.com/users/jakirkham/followers","following_url":"https://api.github.com/users/jakirkham/following{/other_user}","gists_url":"https://api.github.com/users/jakirkham/gists{/gist_id}","starred_url":"https://api.github.com/users/jakirkham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jakirkham/subscriptions","organizations_url":"https://api.github.com/users/jakirkham/orgs","repos_url":"https://api.github.com/users/jakirkham/repos","events_url":"https://api.github.com/users/jakirkham/events{/privacy}","received_events_url":"https://api.github.com/users/jakirkham/received_events","type":"User","site_admin":false},"created_at":"2016-07-12T22:12:52Z","updated_at":"2016-07-12T22:12:52Z","body":"What is `kapsel.yml`? 😕"}}
{"actor":{"display_login":"jakirkham"}}