diff options
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 56 |
1 files changed, 28 insertions, 28 deletions
@@ -3,34 +3,34 @@ 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: - 2.0. download and unpack its control archive - 2.1. store all interest-await file triggers in the file `interested-file` - 2.2. store all interest-await explicit triggers in the file `interested-explicit` - 2.1. store all activate-await file triggers in the file `activated-file` - 2.1. store all activate-await explicit triggers in the file `activated-explicit` - 2.6. remove the downloaded binary package and unpacked control archive - 3. go through `interested-file` and for each line: - 3.1. calculate the dependency closure for the binary package and for - each package in the closure: - 3.1.1. use `apt-file` to get all files of the package - 3.1.2. check if the current file trigger matches any file in the package - 3.1.3. store any hits in the file `result-file` - 4. go through `interested-file` and for each line: - 4.1. calculate the dependency closure for the binary package and for - each package in the closure: - 4.1.1. check if the package activates the current file trigger - 3.1.3. append any hits to the file `result-file` - 5. go through `interested-explicit` and for each line: - 5.1. calculate the dependency closure for the binary package and for - each package in the closure: - 5.1.1. check if the package activate the current explicit trigger - 3.1.3. store any hits in the file `result-explicit` +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 ===== |