On 01/10/2014 01:20 PM, Juan Hernandez wrote:
On 01/10/2014 11:36 AM, Sandro Bonazzola wrote:
> Il 10/01/2014 11:26, David Caro ha scritto:
>> El vie 10 ene 2014 10:50:52 CET, Sandro Bonazzola escribió:
>>> Hi,
>>> can you please create a new gerrit project named ovirt-specs?
>>> it will contain .spec files for needed packages not provided by downstream
distributions.
>>> It will contain:
>>> - httpcomponents-core (needed by java sdk, missing on CentOS)
>>> - httpcomponents-client (needed by java sdk, missing on CentOS)
>>>
>>> It should contain also jasper server, actually in its own repository and
jboss actually packaged by us but without a git repo for the spec file.
>>>
>>> Thanks,
>>>
>>
>> Maybe we can use the existing releng-tools repo to store the external
>> projects specs that we need, I think that as they are part of the
>> release process they fit well there.
>
> looks good to me.
> Juan, can you push needed spec file there?
>
Here they are:
http://gerrit.ovirt.org/23128
Some thoughts on how I would suggest to manage these specs:
- We should have one directory per package, and store in that directory
the template for the .spec file, the build script and also the potential
patches.
- We should have one git branch for each major version of the RPM
distributions that we support. This is what the build systems of Fedora
and RHEL do, for example. So we should have branches like fc19, fc20,
el6, el7, etc. This way it is possible to have different specs for
different distributions without having to use multiple "if fedora/if
rhel" in the spec itself.
- I would even suggest to move the .spec files out from the main
repositories of other components and into this repository. In particular
I would like to do that for the SDKs and the CLI (that is why I
initially suggested to name it "ovirt-specs").
--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.