I agree that the R-Forge system is solid once you have it going but
its better if you are Linux based and less attractive if you are
Windows based. In particular if the two problems I cited before (use
of ssh and the delay) were addressed then together with the key
feature of automatic builds that
Wahou! I did not plan to start such a debate...
It is really not hard to set it up. I am using a vanilla ssh (rather
than putty) and that works fine all the time...
The problem is not how hard or easy it is, the problem is how time
consuming it is.
I am pretty sur that I will manage to make it
I wonder why nobody included the R-forge maintainer in this thread so
far. Let me add Stefan now.
Best wishes,
Uwe
On 28.03.2010 18:34, Henrik Bengtsson wrote:
Hi,
first, r-forge.r-project.org is filling a need and provides a great
service to the community. Please read this thread as since
Hi,
first, r-forge.r-project.org is filling a need and provides a great
service to the community. Please read this thread as sincere feedback
for making it even better, not as a complaint. I fully understand
that r-forge is ran by limited resources and on a volunteer basis.
I'll list some points
> password for every SVN checkout/commit/update.
>
> II.A. GENERATE A PAIR OF PUBLIC/PRIVATE KEYS FOR SSH
> 1. Start PuTTYgen. A 'PuTTYgen Key Generator' window opens.
> 2. Click 'Generate'.
> 3. Follow the instructions, i.e. move the mouse over the panel
PuTTYgen. A 'PuTTYgen Key Generator' window opens.
2. Click 'Generate'.
3. Follow the instructions, i.e. move the mouse over the panel to
generate some randomness. When done, a key is generated.
5. Click "Save private key". Do *not* enter a "key passphrase",
window opens.
2. Click 'Generate'.
3. Follow the instructions, i.e. move the mouse over the panel to
generate some randomness. When done, a key is generated.
5. Click "Save private key". Do *not* enter a "key passphrase", that
is, reply "Yes" to the dialog a
