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

Basic layout of Problem #1

Open
CJ-Wright opened this issue Sep 1, 2017 · 0 comments
Open

Basic layout of Problem #1

CJ-Wright opened this issue Sep 1, 2017 · 0 comments

Comments

@CJ-Wright
Copy link
Member

Building software on CI with complex/changing deps can be rather difficult as one needs to get dependencies from many different (potentially mutually exclusive) sources. I see to major problems here

  1. Package sources: One may want to install some packages from conda, some from pip, some from pip+git and all the combinations there of. This is crucial as one may need the software to be compatible with stable code, rc code, and bleeding edge code simultaneously.
  2. Pinning: One may also need to build against a pinning panoply where pins could be mutually exclusive. Again the pins could come from all sorts of places (and potentially not all places).

Potential structure:

<package name>:
    pip: <pip name>
        versions: [1, 2, 3]
    pip+git: <pip+git url>
    conda: <conda name>
        versions: [1, 5]
...

We may want settings like, pinning=latest which goes with the latest pins and source=cutting edge which goes with as many source installs as possible. We may want a build_all option which reads the requirements, finds all the unique potential builds and runs them all down.

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

1 participant