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

teach remotes about the 'standard' remote type #310

Merged
merged 1 commit into from
Mar 29, 2019

Conversation

kevinushey
Copy link
Contributor

Closes #309.

@@ -166,6 +166,11 @@ package2remote <- function(name, lib = .libPaths(), repos = getOption("repos"),
}

switch(x$RemoteType,
standard = remote("cran",
Copy link
Member

Choose a reason for hiding this comment

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

Well, I don't know if this would cause problems here, but "standard" just means that it was coming from a CRAN-like repo.

I think remotes will be fine with "cran", though....

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I figured this was the easiest way (at least for now) to have remotes just treat these standard remote types as CRAN-like, since cran remotes are already well-understood and handled elsewhere in the system. Do you think this should be handled differently?

At least, I believe this works as a stop-gap solution.

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 it will be fine. I think for remotes "cran" means "cran-like", mostly.

Copy link
Member

Choose a reason for hiding this comment

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

@jimhester do you think this would fail in any way?

Copy link
Member

Choose a reason for hiding this comment

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

Yeah I think this would be fine.

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.

3 participants