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

ensure that the repo passed to url is lowercase #175

Closed
wants to merge 1 commit into from

Conversation

mnel
Copy link
Contributor

@mnel mnel commented Oct 19, 2012

See http://stackoverflow.com/questions/12966600/install-bitbucket-in-devtools-case-sensitive

repo identifiers within url appear to be always lowercase, despite package name.

url <- paste("https://bitbucket.org/", username, "/", repo, "/get/",

# convert repo to lower case in line with bitbucket convention
repo <- tolower(repo)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the identing level is slightly off

@wch
Copy link
Member

wch commented Oct 19, 2012

I have to wonder if this is necessary -- install_bitbucket accesses a repository by name and installs the package from the repo. Why is desirable to change the name of the repo that the user asks for?

@mnel
Copy link
Contributor Author

mnel commented Oct 19, 2012

Because it appears that the repo identifier within the bit bucket URL is all lowercase regardless of the r package name capitalization.

On 20/10/2012, at 2:26 AM, "Winston Chang" <notifications@github.commailto:notifications@github.com> wrote:

I have to wonder if this is necessary -- install_bitbucket accesses a repository by name and installs the package from the repo. Why is desirable to change the name of the repo that the user asks for?


Reply to this email directly or view it on GitHubhttps://github.com//pull/175#issuecomment-9605155.

@wch
Copy link
Member

wch commented Dec 15, 2012

I've implemented this in 14e0631 .

@wch wch closed this Dec 15, 2012
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

Successfully merging this pull request may close these issues.

None yet

3 participants