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

[Doc] how to force rebuild an R package from source #29

Open
JosiahParry opened this issue Apr 4, 2024 · 2 comments
Open

[Doc] how to force rebuild an R package from source #29

JosiahParry opened this issue Apr 4, 2024 · 2 comments
Labels
bug an unexpected problem or unintended behavior

Comments

@JosiahParry
Copy link
Contributor

I want to watch the build process for my R package again to make sure that an environment variable is successfully being passed in. However, I cannot understand the pkgdepends::pkg_refs() documentation linked.

How would one go about forcing the recompliation of a package. From my reading of the dock the below should work.

rwasm::add_pkg("https://github.com/josiahparry/rsgeo?source&nocache")

@JosiahParry
Copy link
Contributor Author

I've tried rm_pkg() but it gave me this message which made me panic and cancel the function while in process. I just spent nearly an hour and a half installing the dependencies for vctrs and would hate to see all of them be delete because I wanted to remove a single package.

image

@georgestagg georgestagg added the bug an unexpected problem or unintended behavior label Apr 4, 2024
@georgestagg
Copy link
Member

georgestagg commented Apr 4, 2024

rm_pkg() is probably the easiest method right now. I'd like to support pkg_refs like nocache here but rwasm has its own caching mechanism that's unaware of those pkg ref attributes currently.

I've marked this as a bug to remind me to revisit the caching mechanism.

Don't worry about the "Processing packages" output, it's not removing those packages. The output is from rebuilding your repository PACKAGES file after removing packages with rm_pkg(). Those files listed are built and existing ones that have been found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants