File: control

package info (click to toggle)
libbio-db-seqfeature-perl 1.7.5-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,108 kB
  • sloc: perl: 9,675; makefile: 2
file content (44 lines) | stat: -rw-r--r-- 1,886 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
Source: libbio-db-seqfeature-perl
Maintainer: Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
Uploaders: Michael R. Crusoe <crusoe@debian.org>,
           Étienne Mollier <emollier@debian.org>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper-compat (= 13)
Build-Depends-Indep: libbio-perl-perl,
                     libbio-db-gff-perl,
                     libdbd-pg-perl,
                     libdbd-sqlite3-perl,
                     libdbi-perl,
                     perl,
                     libtest-most-perl
Standards-Version: 4.7.0
Vcs-Browser: https://salsa.debian.org/med-team/libbio-db-seqfeature-perl
Vcs-Git: https://salsa.debian.org/med-team/libbio-db-seqfeature-perl.git
Homepage: https://metacpan.org/release/Bio-DB-SeqFeature
Rules-Requires-Root: no

Package: libbio-db-seqfeature-perl
Architecture: all
Depends: ${misc:Depends},
         ${perl:Depends},
         libbio-perl-perl,
         libbio-db-gff-perl,
         libdbd-pg-perl,
         libdbd-sqlite3-perl,
         libdbi-perl
Breaks: libbio-perl-perl (<< 1.7.3)
Replaces: libbio-perl-perl (<< 1.7.3)
Description: Normalized feature for use with Bio::DB::SeqFeature::Store
 The Bio::DB::SeqFeature object is the default SeqFeature class stored in
 Bio::DB::SeqFeature databases. It implements both the
 Bio::DB::SeqFeature::NormalizedFeatureI and
 Bio::DB::SeqFeature::NormalizedTableFeatureI interfaces, which means that its
 subfeatures, if any, are stored in the database in a normalized fashion, and
 that the parent/child hierarchy of features and subfeatures are also stored
 in the database as set of tuples. This provides efficiencies in both storage
 and retrieval speed.
 .
 Typically you will not create Bio::DB::SeqFeature directly, but will ask the
 database to do so on your behalf, as described in Bio::DB::SeqFeature::Store.