Why Is libassuan still a static lib? 2009 Edition

[Eric Dorland]

Hello,

When I last brought this up
(http://markmail.org/message/anh6vlx3dx2vdgyq#query:libassuan%20shared%20Eric%20Dorland+page:1+mid:4jfwogujquqaaqnu+state:results),
it was said that libassuan was still a static library because the API
was still not stabilized. It's now 3 years later nearly and as far as
I can tell the API hasn't changed very much. Can we revisit this? I'm
happy to provide the patch :)

--
Eric Dorland <eric@...>
ICQ: #61138586, Jabber: hooty@...



_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@...
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

[Werner Koch]

On Mon, 17 Aug 2009 00:59, eric@... said:

> was still not stabilized. It's now 3 years later nearly and as far as
> I can tell the API hasn't changed very much. Can we revisit this? I'm
> happy to provide the patch :)

It is more than a patch.  Actually we have this in the works for several
months now.  However other projects required too much attention (gpg4win
in particular :-().

More on this soon.


Salam-Shalom,

   Werner

--
Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.


_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@...
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

[Eric Dorland-4]

* Werner Koch (wk@...) wrote:

> On Mon, 17 Aug 2009 00:59, eric@... said:
>
> > was still not stabilized. It's now 3 years later nearly and as far as
> > I can tell the API hasn't changed very much. Can we revisit this? I'm
> > happy to provide the patch :)
>
> It is more than a patch.  Actually we have this in the works for several
> months now.  However other projects required too much attention (gpg4win
> in particular :-().
>
> More on this soon.

What about it is more than a patch to build system?

--
Eric Dorland <eric@...>
ICQ: #61138586, Jabber: hooty@...



_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@...
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

[Werner Koch]

On Mon, 24 Aug 2009 01:04, eric@... said:

> What about it is more than a patch to build system?

We need to define an ABI for the years to come; some old APIs will be
removed, other will undergo minor changes.  Changing an ABI after its
initial release is far more troublesome than changing an API for a
static lib.  Switching to a DSO is a good opportunity to do this.


Salam-Shalom,

   Werner


--
Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.


_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@...
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

[Marcus Brinkmann]

Eric Dorland wrote:

> * Werner Koch (wk@...) wrote:
>> On Mon, 17 Aug 2009 00:59, eric@... said:
>>
>>> was still not stabilized. It's now 3 years later nearly and as far as
>>> I can tell the API hasn't changed very much. Can we revisit this? I'm
>>> happy to provide the patch :)
>> It is more than a patch.  Actually we have this in the works for several
>> months now.  However other projects required too much attention (gpg4win
>> in particular :-().
>>
>> More on this soon.
>
> What about it is more than a patch to build system?

Hi,

as you can see in the SVN repository, there have been extensive changes.  In
particular, one goal was to allow GPGME to use an external libassuan, and that
required replacing some system code in libassuan at run-time on a per-context
basis.

The main changes have been done now, and things seem to work (under GNU/Linux
at least).  More testing has to be done, but we are getting closer.

Please check out the new libassuan interface, and if you can see problems, let
us know.

Thanks,
Marcus


_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@...
http://lists.gnupg.org/mailman/listinfo/gnupg-devel