[pass] Support multiple git repositories

Lenz Weber mail at lenzw.de
Mon Apr 6 14:59:23 CEST 2015


actually, that functionality has already been submitted in November:


somewhere around December Jason stated that he likes the idea, but that
it would need a cleanup:


That cleanup has never been done as far as I know, but that commit from
ruza might be a good starting point to work on from.

Of course, you can also roll your own solution ;)

As for commiting:
git-format-patch is the way to go, other than that, just use the same
type of whitespace/tabs (not sure right now) the rest of the project
uses and you should be golden.
You SHOULD however not that we currently have a long turnabout time
until patches are accepted/integrated into the upstream repo. 
This should not in any means discourage you, just don't get
disappointed if your patch is not integrated within the next two months
- Jason will get to it eventually, but we never know when he has the
time ;)

As for testing:
Just running "make test" in the root dir should suffice for just running
the tests.
The hardcoded GPG ids are included in tests/gnupg/{pub,sec}ring.gpg and
will be used by the tests if you run them from the Makefile.

Handling the settings and CLI:
the less changes you make for settings/parameters, the better your
chances are for the patch to be accepted.
Ideally one would just clone another git repo within the main repo and
password-store would just work with that.

I hope that helps,

Disclaimer: I'm just another mailing-list user, this is no official
statement ;)

Am Mon, 06 Apr 2015 10:00:22 +0100
schrieb Alfredo Palhares <masterkorp at masterkorp.net>:

> Hello everyone,
> I have been using pass for months personally, love the bullet proof
> simplicity. In case everything fails, I can just use GPG directly.
> I would like to use it with my colleagues. But for that I would need
> multi repository support.
> I will be willing to provide a patch, but before starting I have a
> few questions:
> - How to contribute ?
>   After searching on the mailing lists it seems that using
> git-fomat-patch is the way to but, is there any more information on
> what rules shall I follow like in the Linux kernel[1] ?
> - How to write tests ?
>   There are some tests, but I see some what seem to some hardcoded
> gpg key ids. Can someone guide how to successfully run the tests on
> my machine ?
> - Handling the settings
>   My approach to multiple repositories would an main ~/.pass.conf or
>   password-store.conf files and the tree would be in either in
> ~/.password-store or ~/.pass
> - Command line parameters to handle the repositories
>   An extra set of parameters should be included a good example would
> be pass add mycompany <git-repo-remote-url> and the would add the
> remote under ~/.password-store dir
>   A set-default parameter should also be good.
> - Configuration file format
>   What would be a format that would be easy to read and more
> importantly easy to parse by a bash script without adding too much
> complexity?
> What do you guys think of this ?
> [1]
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches?id=refs/tags/v4.0-rc6

More information about the Password-Store mailing list