Sorry, in the sequence of emails the context was probably lost, package ?
package was a side note.
I was referring to (what I believe is a fact) that -package.Rd is not
treated by pkgdown as an
overall package description but package.Rd is and I think that the
recommendation by
Will the package build if you back out the "minor changes"? If so, what
were the minor changes (show diff output)?
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Mon, Sep 30, 2019 at 12:24 PM Steve Gutreuter
wrote:
> I have a package which will no longer build after minor changes. The
>
On Tue, Sep 24, 2019 at 8:07 AM Georgi Boshnakov
wrote:
>
> It is worth noting that
>
> help(package="")
>
> shows file -package.Rd, while
>
> help()
>
> shows topic "package".
>
> Topic -package.Rd is also printed at the top of the pdf manual,
> while package.Rd follows the alphabetical
Is it really called "mypackage"? Otherwise I'd first check that it is spelled
the same way in all cases...
Another possibility is that the embedded spaces in the pathname is doing you in.
-pd
> On 30 Sep 2019, at 16:31 , Steve Gutreuter wrote:
>
> I have a package which will no longer build
Hi Steve,
Is there a reason why your package is called `screenr`, and yet the output
mentions `mypackage` as the name of the package? Did you manually edit the
output? If not, then it would perhaps suggest that you have another description
file lying around in your directory that's causing
I have a package which will no longer build after minor changes. The
problem occurs under both Windows 10 and Linux Mint. For example, from a
Windows terminal I do:
C:\Users\xyz\OneDrive - ORG\Computing\Devel> R CMD build screenr
and I get:
* checking for file 'mypackage/DESCRIPTION' ... OK
*
