Libgcrypt (Compatibility Libraries)

Revision as of 20:01, June 19, 2014 by Drobbins (Talk | contribs) (Drobbins moved page Libgcrypt (Compatibility Libraries) to Package:Libgcrypt (Compatibility Libraries) without leaving a redirect)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

dev-libs/libgcrypt-compat


Current Maintainer(s):Daniel Robbins
Source Repository:Repository:Funtoo Overlay


Summary: Libgcrypt is a general purpose cryptographic library. This version of Libgcrypt is is designed to sit alongside an existing libgcrypt install, and just provide compatibility libs for apps that require an older libgcrypt.


News

Drobbins

IP Space Migration Continues

All Funtoo user containers in the 8.28 IP space will be moving into our new IP space (172.97) over the next few days. If you have DNS set up -- be sure to watch your container and update to the new IP! container.host.funtoo.org DNS will be updated after the move.
2015-08-27 by Drobbins
Drobbins

Funtoo Hosting IP Move

Funtoo user containers with IPs in the 72.18.x.x range will be gradually migrating to new IP addresses this week. If you have DNS entries for your containers, please be aware that your DNS will need to be updated.
2015-08-11 by Drobbins
Drobbins

New ARM Stages

New ARM Stages, built with a new toolchain, are now hitting mirrors. Existing ARM users should re-install using these stages (dated Aug 3, 2015 or later,) rather than upgrade using emerge.
2015-08-06 by Drobbins
More...

Libgcrypt (Compatibility Libraries)

Tip

We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.

This ebuild was added to Funtoo Linux to serve as a compatibility library for binary ebuilds that require an older version of libgcrypt.

This ebuild is designed to install alongside the newer libgcrypt ebuild, providing the older shared libraries only, but no headers, and is designed not to touch the main .so symlink. This way, binary packages can find and use this library just fine, but from-source ebuilds will continue to use libgcrypt.