libecap 1.0.1-3.2ubuntu4 source package in Ubuntu

Changelog

libecap (1.0.1-3.2ubuntu4) jammy; urgency=high

  * No change rebuild for ppc64el baseline bump.

 -- Julian Andres Klode <email address hidden>  Thu, 24 Mar 2022 13:11:37 +0100

Upload details

Uploaded by:
Julian Andres Klode
Uploaded to:
Jammy
Original maintainer:
Ubuntu Developers
Architectures:
any
Section:
libs
Urgency:
Very Urgent

See full publishing history Publishing

Series Pocket Published Component Section
Jammy release main misc

Downloads

File Size SHA-256 Checksum
libecap_1.0.1.orig.tar.gz 331.0 KiB 675f1a40a74a103864cb771ff30162bcdd1caeef4c808799a8293a9e9fe57d8c
libecap_1.0.1-3.2ubuntu4.debian.tar.xz 5.1 KiB 964ee100be12b0aea9eaf9f73e4b2a030db367546c8f38687d6d7280fd49f839
libecap_1.0.1-3.2ubuntu4.dsc 1.9 KiB e9d2860a918a382c1fbbfc5602f3d8e6fe9b0322edd68bba5a349efe34498600

View changes file

Binary packages built by this source

libecap3: eCAP library

 eCAP is a software interface that allows a network application,
 such as an HTTP proxy or an ICAP server, to outsource content
 analysis and adaptation to a loadable module. For each applicable
 protocol message being processed, an eCAP-enabled host application
 supplies the message details to the adaptation module and gets
 back an adapted message, a "not interested" response, or a "block
 this message now!" instruction. These exchanges often include
 message bodies.

libecap3-dbgsym: debug symbols for libecap3
libecap3-dev: eCAP development libraries

 eCAP is a software interface that allows a network application,
 such as an HTTP proxy or an ICAP server, to outsource content
 analysis and adaptation to a loadable module. For each applicable
 protocol message being processed, an eCAP-enabled host application
 supplies the message details to the adaptation module and gets
 back an adapted message, a "not interested" response, or a "block
 this message now!" instruction. These exchanges often include
 message bodies.