You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
I have a legacy package developed without using roxygen for the .Rd files. When I tried to use devtools::release() to submit the package, rogygen2 was run, resulting in an empty NAMESPACE file, with no prompt for 'first time use of roxygen2`. This seems to be a bug, but certainly unexpected.
Is there any way to prevent this?
Warning: DR_DEVTOOLS FOUND PROBLEMS
* R is out of date (3.2.5 vs 3.3.2)
* RStudio is out of date (0.99.1266 vs 1.0.136)
1: Uhhhh... Maybe?
2: I agree
3: I forget
Building and checking HistData ===========================================================================================
Updating HistData documentation
First time using roxygen2. Upgrading automatically...
Updating roxygen version in C:\R\projects\histdata\pkg/DESCRIPTION
The text was updated successfully, but these errors were encountered:
I actually had the same issue, when calling devtools::release() my NAMESPACE was overwritten with a blank one, resulting in some random warnings and notes right before submission. Funny part is that I used roxygen2 to create the initial NAMESPACE anyway, so I'm not sure about the comment 'first time use of roxygen2'
I believe this is a bug, but I got my package submitted using devtools::release(check = FALSE) regardless. I just ran an extra check before submitting.
Edit After a little more digging, it turns out that devtools::release() runs roxygen2::oxygenize() (somehow), therefore the NAMESPACE file is overwritten by one from your roxygen2 comments every time release() is run. I elected not to use any roxygen2 formatting in my package and do it the old fashioned way (e.g. writing .rd files by hand), which burned me here. That being said, simply going through and adding the @importFrom and @export to the applicable functions allowed for a proper namespace to be developed and viola, no, issues with NAMESPACE when running release()
That being said, perhaps there is a way to change release() (or an upstream function) to overlook this for those electing to hand-write their .rd and NAMESPACE files.