-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Drop github dependencies under remotes #32
Comments
Hi @karthik, I've just encountered an issue like this. My
However, these remotes don't seem to be added to the Docker image. Also, if I do Would be great to get this sorted out. Otherwise, this is a very magical package indeed. Thank you! Best regards, Andrew. |
Thanks Andrew! Yes Im aware of these issues and am sorting them out. |
@datawookie Thanks for this issue. I've added this feature in the most recent update. Can you give this a spin and let me know if you run into issues? thanks! |
Thank you for sharing your repo. You helped me uncover a new bug that I'm working through now. |
No problem. Very happy to help with debugging this. Excited to get it working. |
ok @datawookie! I have an update. Try this code: cd /tmp
git clone https://github.com/datawookie/tidytuesday.git
cd tidytuesday
# Launch R
# Make sure you have a recent version of holepunch
x <- holepunch::get_dependencies(".")
rem <- lapply(x, remotes:::package2remote)
rem[[which(x == "pluralize")]] Do you see option A $host
[1] "api.github.com"
$package
NULL
$repo
[1] "pluralize"
$subdir
NULL
$username
[1] "hrbrmstr"
$ref
[1] "master"
$sha
[1] "1c24cd1761d2d57214c2aaeeb234c2c9b7aeba75"
$auth_token
NULL
attr(,"class")
[1] "github_remote" "remote" or Option B? $name
[1] "pluralize"
$repos
CRAN
"https://cran.rstudio.com"
$pkg_type
[1] "both"
$sha
[1] "0.1.0"
attr(,"class")
[1] "cran_remote" "remote"
I am seeing A on a fresh clone. But earlier I saw B, which made it hard to detect that it was a GitHub only package. On further experimentation I am seeing B when I clone |
Hi @karthik, Glad to know that this is moving forward! I just followed your directions and ended up with Option A. Can I assume that this was what you were hoping for? :) Best regards, |
That's right! In that case I will call this issue resolved. Thanks for your help 😄 |
@karthik has this fix been merged into |
It works for me on version |
Currently
write_compendium_description
writes all dependencies together. It would be more useful to separate out remotes and imports.The text was updated successfully, but these errors were encountered: