On 06/01/2011 2:19 PM, Kevin Wright wrote:
Yes, exactly.  But the problem is with NEWS.Rd, not NEWS.

I'm not sure who you are arguing with, but if you do file a bug report, please also put together a simple reproducible example, e.g. a small package containing NEWS.Rd in the inst directory (which is where the docs say it should go) and code that shows why this is bad. Don't just talk about internal functions used for building packages; as far as we can tell so far tools:::.build_news_db is doing exactly what it should be doing.

Duncan Murdoch

pkg/inst/NEWS.Rd is moved to pkg/NEWS.Rd at build time, but for
installed packages, "news" tried to load "pkg/inst/NEWS.Rd".

I'm going to file a bug report.

Kevin


On Thu, Jan 6, 2011 at 7:29 AM, Kevin Wright<kw.s...@gmail.com>  wrote:
>  If you look at tools:::.build_news_db, the plain text NEWS file is
>  searched for in pkg/NEWS and pkg/inst/NEWS, but NEWS.Rd in only
>  searched for in pkg/inst/NEWS.Rd.
>
>  Looks like a bug to me.
>
>  I *think*.
>
>  Thanks,
>
>  Kevin
>
>
>  On Thu, Jan 6, 2011 at 7:09 AM, Kevin Wright<kw.s...@gmail.com>  wrote:
>>  Hopefully a quick question.  My package has a NEWS.Rd file that is not
>>  being found by "news".
>>
>>  The "news" function calls "tools:::.build_news_db" which has this line:
>>
>>  nfile<- file.path(dir, "inst", "NEWS.Rd")
>>
>>  So it appears that the "news" function is searching for
>>  "mypackage/inst/NEWS.Rd".
>>
>>  However, "Writing R extensions" says "The contents of the inst
>>  subdirectory will be copied recursively to the installation directory"
>>
>>  During the installation, mypackage/inst/NEWS.Rd is copied into the
>>  "mypackage" directory, not "mypackage/inst".
>>
>>  What am I doing wrong, or is this a bug?
>>
>>  Kevin Wright
>>
>>
>>
>>  --
>>  Kevin Wright
>>
>
>
>
>  --
>  Kevin Wright
>




______________________________________________
R-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.

Reply via email to