File: control

package info (click to toggle)
libmpack 1.0.5-4
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 296 kB
  • sloc: ansic: 3,634; makefile: 147
file content (55 lines) | stat: -rw-r--r-- 1,777 bytes parent folder | download
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
Source: libmpack
Section: libs
Priority: optional
Maintainer: James McCoy <jamessan@debian.org>
Build-Depends:
 debhelper-compat (= 13),
 libtool-bin,
Standards-Version: 4.6.2
Rules-Requires-Root: no
Homepage: https://github.com/libmpack/libmpack/
Vcs-Git: https://salsa.debian.org/jamessan/libmpack.git
Vcs-Browser: https://salsa.debian.org/jamessan/libmpack

Package: libmpack-dev
Section: libdevel
Architecture: any
Depends:
 libmpack0 (= ${binary:Version}),
 ${misc:Depends},
Multi-Arch: same
Description: small binary serialization/RPC library (development files)
 libmpack is a small binary serialization/RPC library that implements both the
 msgpack and msgpack-rpc specifications.
 .
 Differences from msgpack-c:
 .
  * Callback-based API to simplify (de)serialization directly to/from
    application-specific objects.
  * C89 compatible code
  * No allocation performed by the library, but helpers to simplify dynamic
    allocation if the application needs it.
  * Non-backtracking, incremental/iterative parse/serialization API
 .
 This package contains the headers files needed for developing with mpack

Package: libmpack0
Architecture: any
Pre-Depends:
 ${misc:Pre-Depends},
Multi-Arch: same
Depends:
 ${misc:Depends},
 ${shlibs:Depends},
Description: small binary serialization/RPC library
 libmpack is a small binary serialization/RPC library that implements both the
 msgpack and msgpack-rpc specifications.
 .
 Differences from msgpack-c:
 .
  * Callback-based API to simplify (de)serialization directly to/from
    application-specific objects.
  * C89 compatible code
  * No allocation performed by the library, but helpers to simplify dynamic
    allocation if the application needs it.
  * Non-backtracking, incremental/iterative parse/serialization API