-
Notifications
You must be signed in to change notification settings - Fork 38
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
Ability to override generated source urls #14
Comments
Do you have the link to the github repo for s3fs? Thanks Tom On Mon, Apr 14, 2014 at 5:03 PM, aarondodd [email protected] wrote:
Tom Wilson This e-mail may contain information that is confidential, privileged or |
The project is at https://github.com/s3fs-fuse/s3fs-fuse now, following the googlecode link. The tarball has also changed from "s3fs-version" to "s3fs-fuse-version". The most recent release is https://github.com/s3fs-fuse/s3fs-fuse/releases/tag/v1.76, but I'm not sure how to download directly, the source download link itself doesn't work via curl or the recipe. |
Maybe the recipe should clone the github master and build the source. I Thanks Tom On Mon, Apr 14, 2014 at 5:59 PM, aarondodd [email protected] wrote:
Tom Wilson This e-mail may contain information that is confidential, privileged or |
It be nice if you could use custom url for the install, that way if your using in an production environment you can pull form your own repo, rather then the public one, this limiting upgrade and security risk. |
@SonyDavid i fixed the repo URL in 3.0.0 ( https://github.com/twilson63/s3fs-recipe/releases/tag/v3.0.0 ) |
this should be fixed in latest version: https://github.com/twilson63/s3fs-recipe/blob/master/attributes/default.rb#L42 |
Hi,
s3fs moved from googlecode to github so this recipe fails to install now, and doesn't seem to support supplying a URL (it generates based off version number).
I'm going to fork internally for the moment to specify a local http repository for pulling, but it'd be great if there was support for this in the recipe already.
The text was updated successfully, but these errors were encountered: