blob: da45d5ef08f85e83044e19e95b67833280cbd26e (
plain)
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
|
Running
=======
Just start `./setup.sh`. It will do the following:
1. download apt sources and apt-file data for the amd64 Debian sid snapshot at
`20141211T041251Z` and store them in a directory tree rooted at
`./debian-sid-amd64`
2. go through all binary packages which have a file `DEBIAN/triggers` in their
control archive (the list is stored in the file `control_triggers_packages`)
and for each package:
1. download and unpack its control archive
2. store all interest-await file triggers in the file `interested-file`
3. store all interest-await explicit triggers in the file `interested-explicit`
4. store all activate-await file triggers in the file `activated-file`
5. store all activate-await explicit triggers in the file `activated-explicit`
6. remove the downloaded binary package and unpacked control archive
3. go through `interested-file` and for each line:
1. calculate the dependency closure for the binary package and for
each package in the closure:
1. use `apt-file` to get all files of the package
2. check if the current file trigger matches any file in the package
3. store any hits in the file `result-file`
4. go through `interested-file` and for each line:
1. calculate the dependency closure for the binary package and for
each package in the closure:
1. check if the package activates the current file trigger
2. append any hits to the file `result-file`
5. go through `interested-explicit` and for each line:
1. calculate the dependency closure for the binary package and for
each package in the closure:
1. check if the package activate the current explicit trigger
2. store any hits in the file `result-explicit`
Files
=====
control_triggers_packages
-------------------------
The currently known files that ship a `DEBIAN/triggers` file in their control
metadata. In the future, this list should be autogenerated.
interested-file
---------------
Associates binary packages to file triggers they are interested in. The first
column is the binary package, the second column is either `interest` or
`interest-await` and the last column the path they are interested in.
interested-explicit
-------------------
Associates binary packages to explicit triggers they are interested in. The
first column is the binary package, the second column is either `interest` or
`interest-await` and the last column the name of the explicit trigger they are
interested in.
activated-file
--------------
Associates binary packages to file triggers they activate. The first column is
the binary package, the second column is either `activate` or `activate-await`
and the last column the path they activate.
activate-explicit
-----------------
Associates binary packages to explicit triggers they activate. The first column
is the binary package, the second column is either `activate` or
`activate-await` and the last column the explicit trigger they activate.
result-file
-----------
Associates binary packages with other binary packages they can form a file
trigger cycle with. The first column is the binary package containing the file
trigger, the second column is the file trigger, the third column is a binary
package providing a path that triggers the binary package in the first column,
the fourth column is the triggering path of provided by the binary package in
the third column.
result-explicit
---------------
Associates binary packages with other binary packages they can form an explicit
trigger cycle with. The first column is the binary package interested in the
explicit trigger, the second column is the name of the explicit trigger, the
third column is the binary package activating the trigger.
|