[rkward-devel] a new approach to external plugins

[meik michalke]

hi,

i've now changed my R packages klausuR and koRpus to include the respective 
RKWard plugins directly, residing in the directory 'inst/rkward'. not so much 
because it makes real sense since you can't use the plugins at all without the 
packages, but mostly because it's much easier to maintain and keep them in 
sync (altough both need some updates now).

of course it's still possible to pack them as seperate plugins. but i was 
wondering if it wouldn't be worth a thought to make this the recommended way 
to manage external packages, even if you don't put any additional R stuff in 
the package. i mean, why not simply have R's packaging system manage RKWard's 
add-ons as well? it souldn't be too hard to let RKWard scan (newly installed) 
packages for 'rkward' subdirectories with pluginmaps, maybe use a special 
'src/Makefile' target to add pluginmaps automatically somewhere (which should 
even work in plain R), or even still leave it to GHNS.

all it takes to successfully build and install a new R package seems to be a 
valid DESCRIPTION file. add 'inst/rkward/yourPlugin' to it, and you're done. 
it wouldn't really make things harder for anyone.


viele grüße :: m.eik

-- 
dipl. psych. meik michalke
institut f"ur experimentelle psychologie
abt. f"ur diagnostik und differentielle psychologie
heinrich-heine-universit"at d-40204 d"usseldorf
-------------- 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/20110803/e78ca64e/attachment.sig>