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
|
Source: libgclib
Maintainer: Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
Uploaders: Steffen Moeller <moeller@debian.org>,
Andreas Tille <tille@debian.org>,
Michael R. Crusoe <crusoe@debian.org>
Section: science
Priority: optional
Build-Depends: debhelper-compat (= 13),
d-shlibs
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/med-team/libgclib
Vcs-Git: https://salsa.debian.org/med-team/libgclib.git
Homepage: https://github.com/gpertea/gclib
Rules-Requires-Root: no
Package: libgclib-dev
Architecture: any
Multi-Arch: same
Section: libdevel
Depends: libgclib2 (= ${binary:Version}),
${misc:Depends}
Description: header files for Genome Code Lib (GCLib)
This is an eclectic gathering of (mostly) C++ code which upstream used
for some bioinformatics projects. The main idea is to provide
lean code and efficient data structures, trying to avoid too many code
dependencies of heavy libraries while minimizing production cycles (and
this also implies a decent compile/build time -- looking at you,
bloated configure scripts and lengthy compile times of Boost code or
other heavy C++ template code..).
.
This code was gathered even before the C++ STL had been fully adopted as
a cross-platform "standard". Since STL by itself is a bit heavier for
most of the C++ needs, it is preferred to use simpler&leaner C++ classes
or templates for basic strings, containers, basic algorithms etc.
.
Header files of Genome Code Lib. It is mainly known for being
used by StringTie but with its own release cycle.
Package: libgclib2
Architecture: any
Multi-Arch: same
Section: libs
Depends: ${shlibs:Depends},
${misc:Depends}
Description: C++ library to handle biological short sequence data
This is an eclectic gathering of (mostly) C++ code which upstream used
for some bioinformatics projects. The main idea is to provide
lean code and efficient data structures, trying to avoid too many code
dependencies of heavy libraries while minimizing production cycles (and
this also implies a decent compile/build time -- looking at you,
bloated configure scripts and lengthy compile times of Boost code or
other heavy C++ template code..).
.
This code was gathered even before the C++ STL had been fully adopted as
a cross-platform "standard". Since STL by itself is a bit heavier for
most of the C++ needs, it is preferred to use simpler&leaner C++ classes
or templates for basic strings, containers, basic algorithms etc.
|
