[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=25404#comment-25404 ] 

Barak Korren edited comment on OVIRT-1014 at 1/10/17 3:15 PM:
--------------------------------------------------------------

This had been asked for before.

If the files are exact replicas  symlinks can be used.
WRT hierarchical files, the problem with that is that then it becomes impossible to make certain packages NOT be installed on certain platforms...

WRT having a structured file , this maybe possible - e.g. to keep the existing files as they are and have a new format specified alongside them. But we need to specify this very carefully, and I'm also weary of having too much logic in the CI infrastructure.

Another backwards-compatible possibility to consider - Add an "#include" directive to the packages file.


was (Author: bkorren at redhat.com):
This had been asked for before.

If the files are exact replicas  symlinks can be used.
WRT hierarchical files, the problem with that is that then it becomes impossible to make certain packages NOT be installed on certain platforms...

WTR having a structured file , this maybe possible - e.g. to keep the existing files as they are and have a new format specified alongside them. But we need to specify this very carefully, and I'm also weary of having too much logic in the CI infrastructure.

Another backwards-compatible possibility to consider - Add an "#include" directive to the packages file.

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