File: control

package info (click to toggle)
libcork 0.15.0%2Bds-16
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 2,140 kB
  • sloc: ansic: 12,216; python: 206; sh: 126; makefile: 16
file content (75 lines) | stat: -rw-r--r-- 2,874 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
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
Source: libcork
Section: libs
Priority: optional
Maintainer: Debian Bridges Team <team+bridges@tracker.debian.org>
Uploaders: Roger Shimizu <rosh@debian.org>
Build-Depends:
 check,
 cmake,
 debhelper-compat (= 12),
 pkg-config,
 python3-cram,
 python3-sphinx
Standards-Version: 4.5.0
Rules-Requires-Root: no
Homepage: https://libcork.io
Vcs-Git: https://salsa.debian.org/bridges-team/libcork.git
Vcs-Browser: https://salsa.debian.org/bridges-team/libcork

Package: libcork-dev
Section: libdevel
Architecture: any
Multi-Arch: same
Suggests: libcork-doc
Depends: libcork16 (= ${binary:Version}), ${misc:Depends}
Description: simple, easily embeddable, cross-platform C library (development files)
 It falls roughly into the same category as glib or APR in the C world;
 the STL, POCO, or QtCore in the C++ world; or the standard libraries of any
 decent dynamic language.
 .
 So if libcork has all of these comparables, why a new library? Well, none of
 the C++ options are really applicable here. And none of the C options work,
 because one of the main goals is to have the library be highly modular,
 and useful in resource-constrained systems. You’ll hopefully see how this
 fits into an interesting niche of its own.
 .
 This package provides C header files for the libraries.

Package: libcork16
Architecture: any
Multi-Arch: same
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: simple, easily embeddable, cross-platform C library
 It falls roughly into the same category as glib or APR in the C world;
 the STL, POCO, or QtCore in the C++ world; or the standard libraries of any
 decent dynamic language.
 .
 So if libcork has all of these comparables, why a new library? Well, none of
 the C++ options are really applicable here. And none of the C options work,
 because one of the main goals is to have the library be highly modular,
 and useful in resource-constrained systems. You’ll hopefully see how this
 fits into an interesting niche of its own.
 .
 This package provides shared libraries.

Package: libcork-doc
Section: doc
Architecture: all
Multi-Arch: foreign
Depends:
 libjs-mathjax,
 ${misc:Depends},
 ${sphinxdoc:Depends}
Built-Using: ${sphinxdoc:Built-Using}
Description: simple, easily embeddable, cross-platform C library (documentation files)
 It falls roughly into the same category as glib or APR in the C world;
 the STL, POCO, or QtCore in the C++ world; or the standard libraries of any
 decent dynamic language.
 .
 So if libcork has all of these comparables, why a new library? Well, none of
 the C++ options are really applicable here. And none of the C options work,
 because one of the main goals is to have the library be highly modular,
 and useful in resource-constrained systems. You’ll hopefully see how this
 fits into an interesting niche of its own.
 .
 This package provides documentation in HTML for the libraries.