[
https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jir...
]
Barak Korren commented on OVIRT-1014:
-------------------------------------
{quote}
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.
{quote}
The thing with this is that the '{{*.packages}}' file need to be translated to a
single '{{yum install foo bar baz...}}' line. So there is not much versioning
logic I can do. You can use exact versions though.
I suppose we could implement more complex logic, but that will be equivalent to running
'{{yum-builddep}' from inside the automation script (Which means, the results will
not be cached, and the installation will be done every single time the job runs).
We might be able to do more complex stuff when we get around to OVIRT-873.
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)