[PATCH 0 of 3] hgkeyring extension

[Martin Geisler]

Markus Zapke-Gründemann <markuszapke at gmx.net> writes:

> Pierre-Yves David schrieb:
>> On Fri, Aug 24, 2012 at 11:40:16AM +0200, Markus Zapke-Gründemann wrote:
>> 
>>> This is the port of the mercurial_keyring extension to the core. The new
>>> extension is named hgkeyring.
>> 
>> Which the new name? Aren't Do you break some backward compatibility in the
>> configuration or something ?
> mercurial_keyring is a Python package[1]. You install it with something like:
>
> pip install mercurial_keyring
>
> Then you activate it like so:
>
> [extensions]
> mercurial_keyring =
>
> The rest of the extension's configuration happens in the auth section:
>
> [auth]
> myremote.schemes = http https
> myremote.prefix = hg.example.com/repo
> myremote.username = alice
>
> So users of mercurial_keyring would just have to uninstall the Python package
> and exchange mercurial_keyring with hgkeyring in their extensions section.
>
> IMO it's better to have a different name so users can easily understand which
> extension they are using.

I agree, but for bundling with Mercurial I think the name should simple
be keyring -- the "hg" is redundant. I guess it's okay to call it that
even when there is another keyring package on pypi -- the extension will
be hgext.keyring and thus different from just keyring.

-- 
Martin Geisler
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20120824/28514347/attachment.pgp>