Skip to content
This repository has been archived by the owner on Feb 5, 2024. It is now read-only.

Allow initial library to be unindexed #54

Open
xogeny opened this issue Feb 16, 2014 · 6 comments
Open

Allow initial library to be unindexed #54

xogeny opened this issue Feb 16, 2014 · 6 comments

Comments

@xogeny
Copy link

xogeny commented Feb 16, 2014

It should be possible, as with pip, to install something even if it hasn't been indexed by impact, e.g.,

impact install -e git+https://github.com/xogeny/Sensors.git#/path/to/library

The main application for this, that I see, is the ability to load private libraries on GitHub, but I suspect there will be others. Note, this only works for the initial library to be downloaded. Any other libraries have to be indexed (or else impact can't know about them).

If other private libraries are required, then I see two possible options. First, the user could create a private index file (so that impact could find and load additional dependencies). Second, the user could list additional libraries in the install command as a way to preemptively load dependencies that are private.

@xogeny
Copy link
Author

xogeny commented Feb 16, 2014

Since this is a private repository, the URL will almost certainly require a query parameter with the access token in it, e.g.,

impact install -e git+https://github.com/xogeny/Sensors.git?access_token=...#/path/to/library

@dietmarw
Copy link
Member

At the same time one should be able to put the access token in the config file.

@xogeny
Copy link
Author

xogeny commented Feb 16, 2014

Yes, but the access token in the config file is used when building the index, not when installing.

@dietmarw
Copy link
Member

Yes that's why we would need a second (and a third and a fourth ...) one.

@dietmarw dietmarw added this to the v0.9.0 VCS, asset support milestone Dec 11, 2014
@xogeny
Copy link
Author

xogeny commented Apr 19, 2015

I'm fine with this option, but I think we should put it in a post-conference milestone. Comments?

@dietmarw dietmarw modified the milestones: v1.1.x Post-conference features, v0.9.0 VCS, asset support Apr 20, 2015
@dietmarw
Copy link
Member

I agree that for the conference we should concentrate to have something user oriented in place (i.e., making released libraries installable). All the developer nice-to-haves should be pushed to after the conference at least.

@dietmarw dietmarw modified the milestones: v1.1.x Post-conference features, v0.9.0 VCS, asset support Apr 20, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants