1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
  
     | 
    
      Source: librelp
Section: libs
Priority: optional
Maintainer: Michael Biebl <biebl@debian.org>
Build-Depends: debhelper-compat (= 13),
               autoconf-archive,
               libgnutls28-dev (>= 2.10.0),
               libssl-dev,
               pkgconf,
               procps <!nocheck>,
               python3 <!nocheck>,
Standards-Version: 4.7.2
Rules-Requires-Root: no
Vcs-Git: https://salsa.debian.org/debian/librelp.git
Vcs-Browser: https://salsa.debian.org/debian/librelp
Homepage: https://www.rsyslog.com/librelp/
Package: librelp0
Architecture: any
Multi-Arch: same
Section: libs
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: Reliable Event Logging Protocol (RELP) library
 RELP provides reliable event logging over the network.
 .
 RELP (and hence) librelp assures that no message is lost, not even when
 connections break and a peer becomes unavailable. The current version of
 RELP has a minimal window of opportunity for message duplication after a
 session has been broken due to network problems. In this case, a few messages
 may be duplicated (a problem that also exists with plain tcp syslog). Future
 versions of RELP will address this shortcoming.
 .
 Please note that RELP is a general-purpose, extensible logging protocol. Even
 though it was designed to solve the urgent need of rsyslog-to-rsyslog
 communication, RELP supports many more applications. Extensible command verbs
 provide ample opportunity to extend the protocol without affecting existing
 applications.
Package: librelp-dev
Architecture: any
Multi-Arch: same
Section: libdevel
Depends: librelp0 (= ${binary:Version}), ${misc:Depends}
Description: Reliable Event Logging Protocol (RELP) library - development files
 RELP provides reliable event logging over the network.
 .
 RELP (and hence) librelp assures that no message is lost, not even when
 connections break and a peer becomes unavailable. The current version of
 RELP has a minimal window of opportunity for message duplication after a
 session has been broken due to network problems. In this case, a few messages
 may be duplicated (a problem that also exists with plain tcp syslog). Future
 versions of RELP will address this shortcoming.
 .
 Please note that RELP is a general-purpose, extensible logging protocol. Even
 though it was designed to solve the urgent need of rsyslog-to-rsyslog
 communication, RELP supports many more applications. Extensible command verbs
 provide ample opportunity to extend the protocol without affecting existing
 applications.
 
     |