[
https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jir...
]
danken commented on OVIRT-1014:
-------------------------------
We are using symlinks when possible.
#include "./check-patch.packages"
could work for me. But I would like to be able to specify the version of package, in order
to be able to generate spec file Requires: and BuildRequires: directives.
avoid repetition in automation/*packages
----------------------------------------
Key: OVIRT-1014
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1014
Project: oVirt - virtualization made easy
Issue Type: New Feature
Reporter: danken
Assignee: infra
Currently we have many automation/*packages* files, mostly repeating each other.
Most of the information there is then repeated in vdsm.spec as well.
It would be nice to have a hierarchical way to define packages. E.g. having most packages
in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in
avoid repetition in automation/build-artifacts-manual.packages.el7.
It would be even better to have a single palce (yaml file?) to declare each required
package and its version, for each platform/architecture. We can then use it to generate
the spec file.
--
This message was sent by Atlassian JIRA
(v1000.670.2#100024)