Andreas Enge writes:

> Hello Jessica,
>
> a quick reminder, it would be a pity to drop an almost finished package.
>
> Andreas
>
> On Wed, Feb 17, 2016 at 07:13:44PM +0100, Andreas Enge wrote:
>> On Tue, Feb 09, 2016 at 11:55:51PM +0100, Andreas Enge wrote:
>> > Since I tried out a few things, I realised I might as well send you my
>> > modified version of the patch. Maybe you could continue from there and
>> > examine the tests. If you are not happy with some of my modifications,
>> > please feel free to discuss them.
>> did you find some time to look at the password manager recipe? I think it
>> would be nice to get it into our distribution.

Hey,

The tests were failing due to a missing `which` command which I have
added however, it requires `which` as it tries to detect for itself the
GPG command.

The Guix build system therefore can't patch it, this really leaves the
only option of patching the script to use paths so it can be patched or
to use autoconf to detect them upon build so no patching would be
necessary.

I was going to create a patch for this so autoconf was used to detect
what it needs and send this patch upstream however upon looking through
the archives of its mailing list I've found the lead developer is
opposed to this and has make it clear they're not open to discussing
this further:

> I will not be incorporating m4, dot-in extensions, or any thing of the
> sort. That is non-negotiable, and I will not discuss it further.
https://lists.zx2c4.com/pipermail/password-store/2014-April/000751.html

> The whole notion here is that I don't want there to be a "build step",
> ever. This whole platform-file wonkiness was an unfortunate necessity, but
> I don't want to follow that further. There's "running", which is
> src/password-store.sh, and there's "installing", which is putting that file
> as /usr/bin/pass, and that's it. Simplicity is key. Somewhere along the way
> I had to sneak in a little sed into the "installing", which is a bummer,
> but, bleh.
https://lists.zx2c4.com/pipermail/password-store/2014-April/000757.html

In my opinion this while could be fixed downstream isn't worth it to me,
there are plenty of other password managers which don't require this and
operate in a more sensible way. I'll be looking to migrate to another
password manager rather than continue to use this.

I've attached the package so if someone would like to continue, please
do so, I won't be. Thanks for your work and suggestions those who've
helped me get this far with packaging it :) I've learnt a lot about it.

--
Thanks,
Jessica.