On Jan 15, 3:52 pm, "Edward K. Ream" <[email protected]> wrote:
> 4. Use bzr to pull down the leo-editor branch.  This is highly
> recommended because Leo 4.7 b1 is about 6 months old.  As usual, the
> initial install of bzr is a bit of a pain: you may have to create rsa
> public/private keys and tell launchpad about them.  The essential
> command is:
>
> ssh-keygen -t rsa
>
> Do *not* create a pgp key: bzr requires an rsa key.  There are
> excellent instructions 
> athttps://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair
> You can follow, as I did, the instructions for ubuntu.
>
>  ...
>
> 1. It's clear that forcing people to install bzr is a big barrier.  I
> get annoyed every time I have to generate an ssh key.  It's getting
> easier, but it is never fun. The reinforces the need for a b2 release
> asap.
>

I think this is not mandatory if one just want to pull some code from
launchpad. Retrieving a versioned source code tree is similar to
downloading a source code tarball. It's a read-only operation. You
don't have to be logged into launchpad in order to do that.
Authentication via ssh keys is required only for write operations
(push).

However, the requirement about having bzr installed still applies.
Some people might install bzr for the first time just for retrieving
the source code of leo. I was one of those guys myself :) Frankly, I
strongly disagree that installing bzr is a barrier. It was the first
distributed version control system that I've touched. Nowadays I store
a lot of personal data, including source code and leo outlines in bzr.
Learning the basics of it pays off greatly. And it takes about one
hour.
-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.


Reply via email to