Update r-usethis from 3.2.1 to 3.2.2

[emscripten-forge-bot]

Beep-boop-beep! Whistle-whistle-woo!

[emscripten-forge-bot]

Either the CI is failing, or the recipe is not tested. I need help from a human.
Ping the maintainers: @rgaiacs
If you believe you are wrongly pinged, please comment here or open a PR removing you from the maintainers list.

[MMesch]

Either the CI is failing, or the recipe is not tested. I need help from a human.
Ping the maintainers: @rgaiacs
If you believe you are wrongly pinged, please comment here or open a PR removing you from the maintainers list.

[rgaiacs]

@IsabelParedes what is the procedure to update patches? Given that the source code is downloaded from a zip file, there is no version control help for the patch.

[IsabelParedes]

@IsabelParedes what is the procedure to update patches? Given that the source code is downloaded from a zip file, there is no version control help for the patch.

There are multiple options, you can pick depending on your workflow preferences. Here are the 2 options I generally use:

1. Start with the zip file

• Download the zip file and extract the contents
• cd into that directory
• git init and git add . and git commit -m "First commit" : you're essentially starting a new repo
• Apply the patches one at a time and see what changes are rejected. Some useful commands: git am foo.path or git apply --reject foo.patch.
• Once you've applied all patches, simply use git format-patch HEAD~X -o ./patches to generate all the new patches where X is the number of patches.

2. Use the upstream source

• Clone the upstream repo (https://github.com/r-lib/usethis/tags)
• Checkout the tag associated with the version you want to use git checkout <tag-name> (https://github.com/r-lib/usethis/tags)
• Same as above, apply patches and then generate the new patch files

---

If you're building on your local machine

• you can comment out the patches in the recipe
• insert anything at the top of the build script to make it fail (script: gibberish && $R CMD INSTALL $R_ARGS .
• navigate to the work/ directory
• do git init and everything else as in option 1.
• And this also gives you the option of testing if it builds properly.

There are more options out there. You can also maintain a fork of the package with the patches, and then rebase a branch in that fork whenever there is a new release.

Hope this helps!

[rgaiacs]

Thanks! I wanted to make sure that I would not do the wrong way and send a pull request. I will resolve this next week. Have a lovely weekend.