File: README.Debian

package info (click to toggle)
debnest 0.0.10
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 536 kB
  • ctags: 29
  • sloc: sh: 414; makefile: 70
file content (94 lines) | stat: -rw-r--r-- 2,690 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
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
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94

* How to use debnest

 1) `include /usr/share/debnest/debnest.mk' in debian/rules
 2) put Build-Depends[-Indep]: debnest in debian/control

 That's all.

 If you have a generated debian source package including .dsc,
 orig.tar.gz and diff.gz (or tar.gz for native package), then
 invoke debnest_make <.dsc> to create a nested source tree.

* How to use debnest via cdbs (Common Debian Build System)

  * Invoke debnest_make with DEBNEST_RULES='rules-cdbs' environment
  variable.

  * Add Build-Depends[-Indep]: cdbs

 If you use debnest by hand:

  * Add Build-Depends[-Indep]: debnest, cdbs

  * Put all debian source packages including .dsc, .orig.tar.gz, 
    diff.gz in source top directory.

  1) To use nested original binary packages itself

       include /usr/share/cdbs/1/rules/buildcore.mk
       include /usr/share/cdbs/1/rules/debnest.mk

   If you want to select which packages are built by
   debnest, then specify it in 'cdbs_debnest_packages'
   like:

     cdbs_debnest_packages := debnest

   after 'include /usr/share/cdbs/1/rules/debnest.mk'.

  2) To use only contents of nested binary packages

       include /usr/share/cdbs/1/rules/buildcore.mk
       include /usr/share/cdbs/1/class/debnest.mk
       include /usr/share/cdbs/1/rules/debhelper.mk

   This uses only contents of nested binary packages and
   unpacks them into debian/tmp or debian/<package>.

   You can use debhelper to create your own packages from
   the contents.

   rules/debnest.mk includes all the necessary targets from
   .dsc to .deb. On the other hand, class/debnest.mk includes
   only targets to build binary files and install them under
   the package build directory (usually, debian/tmp) and doesn't
   install any DEBIAN control files. You can use class/debnest.mk
   as you use aother cdbs class such as class/makefile.mk

* Your own unpack script

 If debian/debnest-unpack-script exists, then it's invoked
 before unpacking any *.dsc files. You can unpack other files
 by using this. This script must handle the following arguments:

  1) <unpack_script> unpack <source_dir>

    Unpack your own script under the <source_dir>.

  2) <unpack_script> builddir

    List all directories where this script unpacks its sources.

* Some hooks

 In addtiion, you can define the following targets:

 debnest-binary-arch-misc:

  Specify your own binary-arch target.

 debnest-binary-indep-misc:

  Specify your own binary-indep target.

 debnest-build-misc:

  Specify your own build target.

 debnest-clean-misc:

  Specify your own clean target.

$Id: README.Debian,v 1.8 2003/05/29 07:18:29 taru Exp $
                                          Masato Taruishi <taru@valinux.co.jp>