Re: [R] problem in building an R package

2009-11-25 Thread Uwe Ligges



clue_less wrote:

i am trying to build an R package and submit to CRAN.
i am using -
package.skeleton(name=xxzz, code_files = H:\xxzz.R)
to build package xxzz.
---
The code above generates 'xxzz' folder.
It seems that I have to manually edit the files generated in xxzz folder (to
add titles, authors, etc)
--

But when I re-run -
package.skeleton(name=xxzz, code_files = H:\xxzz.R)



Why do you rerun it once you have the structure of your package?
You can add separate files now and add documentation via prompt().

Uwe Ligges




All the edited information will be lost since the default files are 
regenerated such as DESCRIPTION file.


---

I have found the process of building package is extremely troublesome.

Have anybody had a better approach?

Thanks.







__
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.


[R] problem in building an R package

2009-11-24 Thread clue_less

i am trying to build an R package and submit to CRAN.
i am using -
package.skeleton(name=xxzz, code_files = H:\xxzz.R)
to build package xxzz.
---
The code above generates 'xxzz' folder.
It seems that I have to manually edit the files generated in xxzz folder (to
add titles, authors, etc)
--

But when I re-run -
package.skeleton(name=xxzz, code_files = H:\xxzz.R)

All the edited information will be lost since the default files are 
regenerated such as DESCRIPTION file.

---

I have found the process of building package is extremely troublesome.

Have anybody had a better approach?

Thanks.





-- 
View this message in context: 
http://old.nabble.com/problem-in-building-an-R-package-tp26506174p26506174.html
Sent from the R help mailing list archive at Nabble.com.

__
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.