Re: Stable GnuPG interface, git should use GPGME

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am Mittwoch 22 März 2017 18:15:36 schrieb Werner Koch:
> On Fri, 17 Mar 2017 10:56, bernhard.reiter@xxxxxxxxxxxxx said:
> > As the command line is not a stable API to GnuPG, there were changes and
> > there will be changes to the command line over several versions. It maybe
> > in the
>
> That is not true.  The command line interface has been stable for the
> last 19 years.  We only removed a left over PGP-2 backward compatibility
> in 2.1 (-kvv).  I doubt that this has even been noticed.

I was under the impression (and I do remember you telling me a few times)
that the output of the command line interaction did change a lot over times
and using applications had issues. I've experienced a few of those over the 
last 17 years. :) Still I would have to dig up the examples.
You seem to refer more to the existence and principal meaning of command line 
options, which is very stable because of your efforts, which I've mentioned 
before. Contents of the resulting input and output strings has changed though 
and gpgme does this parsing for a using application in a more stable way.

Best Regards,
Bernhard

-- 
www.intevation.de/~bernhard (CEO)     +49 541 33 508 3-3
Intevation GmbH, Osnabrück, Germany; Amtsgericht Osnabrück, HRB 18998
Owned and run by Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

Attachment: signature.asc
Description: This is a digitally signed message part.


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]