-
Notifications
You must be signed in to change notification settings - Fork 525
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
Reference a whole GITHUB repo in paket.dependencies #113
Comments
This may be a bit too much with what you're thinking, but perhaps it can download the archive and extract it? |
that sounds like a good idea. Anything else? |
Yeah I looked at this. The only two options I came up with was either: -
I'm somewhat wary of the API because of the rate limiting - I fell foul of it quite quickly when playing around with it. Also - downloading the whole archive isn't a bad idea but might people want to do folder paths etc. in the future? Or perhaps leave that for a separate issue. |
For the folder paths, perhaps that can be an additional option to specify the location? |
A quick brain dump:
I'm not sure about this, I'd suggest getting in touch with support@github.com. |
@forki I believe the bulk of the concerns in here apply across all file sources and the basic functionality can be expressed as a subsyntax of #154. Hence I'd suggest either closing this to shorten the list or rebasing it to express just a set of concerns related ot multiple files or a syntax proposal (either in terms of #125 or #154 or something else)? |
No the problem here is not syntax in any of the paket files. It's how to get the remote files. That's more technical aspect. |
@forki my point is that there are 2 source syntax proposals and this touches on syntax and on the surface this issue as it is described looks like one but isnt Download rate limiting and caching / fallback support are shared with single file downloads (and genning / caching So I was just saying that it would be best for this isssue to have a clear purpose, be that or fallbck/cachingn or, most likely dealing with rate limiting re github. In which case I'd retitle this "Handle Github rate limiting gracefully for files and/or full-repo source references", not "Reference a whole GITHUB repo in paket.dependencies" |
@forki what are the drawbacks to using |
@forki BTW, it is possible to download |
cool https://github.com/fsprojects/Paket/archive/80795aa62ef8efbb97993e18fc52dd40f7d837c7.zip works. then it will be easy. |
At the moment we can do:
and link this file in a project by adding
File:FsUnit.fs
to the paket.references file. That's really really cool and I documented this at http://fsprojects.github.io/Paket/github_dependencies.html.No I'd like to go one step further and just have
in paket.dependencies.
This should download all files from the repo. For this step I'd keep the paket.references untouched.
Ideas how to download the whole repo without using git?
/cc @agross @isaacabraham
The text was updated successfully, but these errors were encountered: