[rkward-devel] first RKWard enhancer on CRAN

[Thomas Friedrichsmeier]

Hi,

On Monday 12 September 2011, meik michalke wrote:
> works great! one minor thing: it would be interesting to see the names of
> the packages the info message is referring to.

the dialog now lists the added pluginmap files.
 
> > > 2) A repository for RKWard plugins packages which should not (yet) go
> > > to CRAN for whatever reason (as a drop-in replacement for the current
> > > GHNS repository)
> > 
> > yes, that i can do in no time.
> 
> should this repository be part of the rkwardextras project on sf.net? all
> we'd need is an accessible folder for a hierarchy like this:

Yes, that's possible and reasonable. It does not have to be rkwardextras, 
though. The only reason for rkwardextras is to split stuff that might contain 
strong cryptography in any form (as the installation bundle does) into a 
separate location, as SF will block access to such projects from certain 
countries based on US export regulations. Sort of silly, but alas...

Anyway, as long as sources do not include crypto code, and binaries are not 
linked against crypto libraries, packages can go to the rkward project.

Either way, you can access the project web space as
sftp://USERNAME,rkward@web.sourceforge.net/home/groups/r/rk/rkward/htdocs/
see also: http://sourceforge.net/apps/trac/sourceforge/wiki/Project%20web .

> one more thing on that: there is an official package type "Frontend",
> should we use that one for packages without real R payload? from the
> description i think it would fit:
>  o http://cran.r-project.org/doc/manuals/R-exts.html#Frontend

I'm not sure, what this is for, but I guess it's probably meant for complete 
GUIs. Also, I'm not sure, whether I understand the description correctly, but 
it sounds to me like this would require a custom makefile in all cases?

> the PACKAGES files can be updated by
>   write_PACKAGES(repo_sub_dir, type=XXX, latestOnly=FALSE)
> from the tools package, where XXX must be one of "source", "mac.binary" or
> "win.binary", depending on where "repo_sub_dir" points to.
> 
> you can then add http://example.com/<repo_root> to your repo list and
> install the listed packages.

Ok, ideally, in the mid term, we should have (a) script(s) that developers can 
use to add / update / remove packages in the repository in a mostly automated 
fashion. How much of that does your roxyPackage-package cover, yet?

Regards
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/rkward-devel/attachments/20110913/f84d58cb/attachment.sig>