Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependencies #7

Open
minrk opened this issue May 23, 2018 · 1 comment
Open

Dependencies #7

minrk opened this issue May 23, 2018 · 1 comment

Comments

@minrk
Copy link

minrk commented May 23, 2018

Relevant to jupyterhub/repo2docker#309

As a "reproducible document archive" is it in scope for DAR files to include an environment specification (packages, runtime versions, etc.), or is that expected to be left to other tools, such as pip requirements.txt and/or conda environment.yml as neighboring files, not in the archive itself? If so, how is that specified? For Jupyter, we consider this to belong as a sibling of the document, but I think the scope of Jupyter notebooks is meant to be a bit narrower than DAR.

@michael
Copy link
Member

michael commented May 23, 2018

Hi @minrk! This is something we haven't decided on yet. It's being discussed here:

https://docs.google.com/document/d/1-aF637_bbdWtWS11BaO4pEzmAOUozQkt1rum4w7m0mU/edit#heading=h.qxc3j9ll1wn8

One idea was to only provide a runtime identifier and a version. And then there would need to be some kind of registry to resolve and download/install that runtime. This is probably very related to Binder and we're open to any solution that's does the job in a generic way. Like not locking into some concrete technology too much.

In an abstract way there could be a runtime provider, which i can ask: "please provide me runtime x at version y and tell me when ur ready to connect". We'd want a solution that can be used locally on a machine, or as an online service to connect to.

Have any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants