Merge ~litios/ubuntu-cve-tracker:aliases-customer-ppa into ubuntu-cve-tracker:master
Status: | Merged |
---|---|
Merge reported by: | David Fernandez Gonzalez |
Merged at revision: | b967ba813d484b6c1ab52c4afa0f8113351528b5 |
Proposed branch: | ~litios/ubuntu-cve-tracker:aliases-customer-ppa |
Merge into: | ubuntu-cve-tracker:master |
Diff against target: |
116 lines (+64/-1) 4 files modified
scripts/check-syntax (+36/-1) scripts/check-syntax-fixup (+8/-0) scripts/cve_lib.py (+6/-0) scripts/source_map.py (+14/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Eduardo Barretto | Approve | ||
Review via email: mp+434109@code.launchpad.net |
Description of the change
This is the first approach to handle the aliases for projects where the name of the package is specific to it. For example, in project test package foo is actually named test-foo.
I'm relying on the structures that already exist for handling subprojects and adding a new field for taking care of the aliases for the packages.
We discussed naming them boilerplates but I wasn't sure about that because of the already existing boilerplates and because it's a different unrelated thing.
The solution detects if an aliases.yaml exists in the project and performs extra operations according to the aliases specified. Only two extra checks are performed: are all the aliases in the CVE and does the original package name appear (if not specified as an alias)?
The yaml file would be a list of packages and an array of aliases like:
```
foo: ["test-foo", "test2-foo"]
bar: ["test-bar", "test2-bar", "bar"]
```
As I said in the beginning, this is more of a first idea and I would love to get input from people with more experience with UCT.
in boilerplates we have the "release" as part of the structure. Here we have package to package mapping. Could this create some kind of issue? I can't think of one right now, so just trying to brainstorm.