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
|
# Generate packaging example log data
The source package examples are here. These are used to produce log data in advance.
source package name: debhello
executable command name: hello
## Setup
Please make sure to setup packages
```sh
$ make deps
```
## Pre-pre-build (update date etc. in source.)
After making manual changes to *examples/Makefile* and *examples/template/** on date, policy version, etc., update template upstream source examples with:
```sh
$ make groom
```
## Pre-build
Prior to the packaging, the up-to-date packaging example logs need to created
as pre-build under Debian *sid/unstable* chroot environment and committed to
the source tree.
This pre-build chroot environment requires many packages related to
the source building infrastructure.
In this sub-directory:
```sh
$ make
$ make clean
$ git add -A .
$ git commit -m "Update example logs"
```
## Debug pre-build for partial build log examples
If you want to create only a partial packaging example logs for
debugging, you can do it as:
```sh
$ make clean
$ make prep
$ cd debhello-1.6_build-1
$ make
```
## Notes on file organization
### Files in `template/`
This directory contains a set of template files used to be copied to
`debian/*` files of many examples of the packaged source tree.
The changelog file in this template/ is for the latest version of the
package example which is split up properly for each version and copied
accordingly.
### Files in `debhello-<version>/`
Each of these contains an entire set of an example source tree with template
for properly packaged `debian/*` files.
The upstream tarballs used in the packaging example are generated by the tar
command while excluding the debian/ directory.
### Files in `debhello-<version>_build-<revision>/`
These are used to generate the packaging process example.
These contain `step<number>.cmd` files which are executed sequentially and the
results are logged to the step<number>.log files with the script program.
Since the `step<number>.log` files are terminated by `<CR><LF>`, may contain
`<TAB>`, and may be too long, the filtered `step<number>.slog` files are generated.
The `<revision>` is usually 1 and it matches the Debian revision of the binary
packages generated.
If you wish to run script-by-script, you can do the following
```
$ make step<number>.cmd
```
<!-- vim:se tw=78 sts=4 ts=4 et ai: -->
|