[JIRA] (OVIRT-1014) avoid repetition in automation/*packages

[Barak Korren (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25409#comment-25409 ] 

Barak Korren commented on OVIRT-1014:
-------------------------------------

{quote}
the translation of *.pacakges to yum command may include more than `cat`. each line may look like

python-pthreading >= 0.1.3-3
{quote}

I don`t think yum supports something like '{{yum install python-pthreading >= 0.1.3-3}}'. So I can't really do anything useful with such a syntax ATM. I could try to just ignore the version specification when setting up mock, but that may lead to unexpected results.

> 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)