File: control

package info (click to toggle)
jhbuild 3.38.0-3
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 11,532 kB
  • sloc: python: 11,624; sh: 4,548; makefile: 204; ansic: 19; sed: 16
file content (46 lines) | stat: -rw-r--r-- 1,790 bytes parent folder | download | duplicates (2)
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
# This file is autogenerated. DO NOT EDIT!
#
# Modifications should be made to debian/control.in instead.
# This file is regenerated automatically in the clean target.
Source: jhbuild
Section: devel
Priority: optional
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Uploaders: Emilio Pozuelo Monfort <pochu@debian.org>, Jeremy Bicha <jbicha@debian.org>, Jordi Mallach <jordi@debian.org>
Build-Depends: debhelper-compat (= 13),
               dh-sequence-gnome,
               dh-sequence-python3,
               pkg-config,
               trang <!nocheck>,
               yelp-tools
Standards-Version: 4.4.0
Vcs-Git: https://salsa.debian.org/gnome-team/jhbuild.git
Vcs-Browser: https://salsa.debian.org/gnome-team/jhbuild
Homepage: https://wiki.gnome.org/Projects/Jhbuild

Package: jhbuild
Architecture: all
Depends: ${shlibs:Depends},
         ${misc:Depends},
         ${python3:Depends},
	 python3-distutils,
Recommends: git-core,
            patch,
            wget | curl,
            autoconf,
            automake,
            gettext,
            meson,
            pkg-config
Suggests: graphviz
Description: flexible build script for package collections
 Jhbuild is a program that can be used to pull a number of modules from
 Git, CVS, Subversion, Bazaar and other types of repositories or from
 tarballs and build them in the correct order.  Unlike some build
 scripts, jhbuild lets you specify what modules you want built and it
 will then go and build those modules plus dependencies.
 .
 Although jhbuild was originally developed to build GNOME, it has
 since been extended to work with other projects as well.
 Extending it to handle new modules is usually trivial assuming the
 build infrastructure matches the other modules it handles.