libgpg-error: add a static lib to the installation

[barracuda156]

Is it possible to install both dynamic and static libs?

[Schamschula (Marius Schamschula)]

Yes: --enable-static. It is disabled by default.

[barracuda156]

Replying to Schamschula:

Yes: --enable-static. It is disabled by default.

Is if fine to enable it by default or make a non-default variant? Instead of locally hacking the port.

[Schamschula (Marius Schamschula)]

I would prefer a non-default variant.

Static libraries should only be used for bootstrapping within MacPorts.

[barracuda156]

Replying to Schamschula:

I would prefer a non-default variant.

I just thought that this will make it impossible to depend on it for another port. Still better than nothing, of course.

Static libraries should only be used for bootstrapping within MacPorts.

Numerous ports in fact install both.

[ryandesign (Ryan Carsten Schmidt)]

It has been a de-facto standard in MacPorts ports since forever to install static libraries as well, when possible, although I don't know who actually needs static libraries. (In cmake, it's not typically possible without some workarounds, but this software use autotools where it's typically easy, as shown in ​the PR.) We don't hide static libraries in a variant because that makes it impossible for it to be used as a dependency.

If you think this practice should be changed, please gain consensus about that on the mailing list first. We should be consistent about this across the ports collection.

[Schamschula (Marius Schamschula)]

I stand corrected.

[herbygillot (Herby Gillot)]

In 9352521cfca366b2a4b4ac6cb76d66dd34b804a9/macports-ports (master):

libgpg-error: additionally build static libs

Fixes: #67950