RKWard and R emerge ports

[Thomas Friedrichsmeier]

Hi!

After hours of compiling all dependencies, I put together emerge scripts for R 
(utilizing the binary installer) and RKWard (compilation from SVN sources). 
See the attached diff.

Last time I was asking (and ranting) about how to distribute windows binaries, 
I was told to go this way. I must admit, I still don't quite understand, 
whether or not, or under what circumstances "external" projects can become 
part of the "official" kde-win-installer, but ultimately that is my goal. Please 
let me know, whether I am on track for that, what else I would need to 
provide, or what I should aim for, instead.

Some more detailed questions:
1. Which section should this go to (in "testing" right now)? "contributed"?
2. Both emerge scripts contain some portions that seem rather hackish to me. 
See the comments contained within the diff. Any guidance on that?
3. Is it ok to commit this?
4. Will this get part of the nightly builds?

An issue report:
At least strigi and kdelibs look for libbz2. On my system a LIBBZ2.DLL was 
already installed in c:\windows\system32 . Despite %KDEROOT% sitting earlier 
in the PATH, cmake picked up this DLL. The build then failed when trying to 
link it. Temporarily moving c:\windows\system32\LIBBZ2.DLL out of the way 
solved the problem.

Regards
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: portage.diff
Type: text/x-patch
Size: 5033 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-windows/attachments/20100309/e88f961e/attachment.diff 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-windows/attachments/20100309/e88f961e/attachment.sig