| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
This is still really only testing that the object constructed in the
right way and is providing the expected interface and internals as
functions. It needs to actually run as much as possible. I still have to
figure out how to mock that up cleanly.
|
|
|
|
|
|
|
| |
It may be possible to go back further, but I'm tying myself in knots
trying. Might have another go later. Dropped Const::Fast dependency even
though it can be installed on 5.8.1; seems silly for one numeric
constant. Just told Perl::Critic to turn a blind eye.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Default signing to off; step 1 to mitigating the terrible literal
passphrase passing.
|
| |
|
|
|
|
| |
Just pod2markdown of the module documentation
|
|
|
|
|
|
|
|
|
|
|
| |
This still needs a lot more work before release. In particular, I have
to figure out what I'm going to do about the `passphrase` option. It's
probably better to both not require it, in which case no signing is done
(only encryption), and to instead allow a path to a file to be
specified.
The other big puzzle would be how on earth to write automated tests for
it... I may end up imitating however Mail::GnuPG is testing itself.
|
|
|
|
| |
Turned out not to be such a good idea
|
| |
|
| |
|
|
|
|
| |
At request of possible contributor
|
|
|
|
|
|
|
|
|
|
|
| |
IPC::Open3 is recommended by Perl::Critic, but it's a relatively
low-level tool that requires system select() calls and careful
attention to buffering/blocking, among other things. It looks like it's
great if you need fine-tuned detail like that, but in this case, I
don't, I just need something better than system() that will capture both
stdout and stderr from a call.
IPC::Run3 is by the same author and much better suited to this purpose.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
Very bare bones at the moment. Needs perldoc or man(1) help and possibly
a Makefile to install it.
|