Port details |
- libassuan-1 IPC library used by GnuPG and gpgme
- 1.0.5 security
=0 1.0.5Version of this port present on the latest quarterly branch. - Maintainer: dougb@FreeBSD.org
 - Port Added: 2010-06-14 00:43:12
- Last Update: 2010-08-08 20:36:39
- SVN Revision: UNKNOWN
- Also Listed In: devel
- License: not specified in port
- Description:
- This is the IPC library used by GnuPG 1.9, gpgme and the old newpg
package.
cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- libassuan-1>0:security/libassuan-1
- No installation instructions:
- This port has been deleted.
- PKGNAME: libassuan-1
- Flavors: there is no flavor information for this port.
- distinfo:
- There is no distinfo for this port.
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:

- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Library dependencies:
-
- pth.20 : devel/pth
- There are no ports dependent upon this port
Configuration Options:
- No options to configure
- Options name:
- N/A
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 2
Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
Commit | Credits | Log message |
1.0.5 08 Aug 2010 20:36:39
 |
dougb  |
As previously advertised, remove the old libassuan port now that all
consumers have moved to libassuan 2.0.0, or dropped the dependency |
1.0.5 14 Jun 2010 00:42:52
 |
dougb  |
Update security/libassuan to version 2.0.0, which is required by gnupg 2.0.15
Unfortunately version 2.0.0 is largely incompatible with version 1.x, so it
is necessary to have a stopgap measure while ports that depend on libassuan
can be updated. In conversation with the maintainers of the dependent ports
it was originally considered ideal to prepare updates for the ports first,
then upgrade everything to libassuan 2.x en masse. Since no action has
arisen on that front, go with plan B:
Copy security/libassuan to security/libassuan-1, and update the dependent
ports accordingly. Because this is (intended to be) a _temporary_ measure,
and because no updates for libassuan 1.x are anticipated, and because the
hope is that it can be removed sooner rather than later, it's a copy instead
of a repocopy. |
Number of commits found: 2
|