[Engine-devel] ovirt-specs project needed

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, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --DWffXqb4gEk6GX3kuw0BXBg6TsAW2r9Jv Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable El vie 10 ene 2014 10:50:52 CET, Sandro Bonazzola escribi=C3=B3:
Hi, can you please create a new gerrit project named ovirt-specs? it will contain .spec files for needed packages not provided by downstr= eam 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 an= d 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=20 projects specs that we need, I think that as they are part of the=20 release process they fit well there. -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --DWffXqb4gEk6GX3kuw0BXBg6TsAW2r9Jv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJSz8q5AAoJEEBxx+HSYmnDaNEH/0u6DSxWS06plED4+lJLvr74 u49FaV+TSqRloTHyrQWsz04s+nquejP/WrtSSgtT4ZsPXs9D4GgUUDSXYgnnP688 idRJkzzGCtRwFKgx0AfT3l/FK1CBYWW3IybjJKfvLn6NbNqmVVELe0TKHmU3ntNv 3K0wKETZvIfvQkzLqs+1b4XQ+dRmU8DvDnU+iV+zLSBfhdCQUPDqWmteZA57nDu2 fCHshXUGNbdGA5okVu9+C17vpAl6gog0YiJeKAVF3I/QD6JUyeqY5S9DiVwqna17 TfKytjIQAmSutD2ovXLRash4GKfmwCS6v6R7CJaffhB0OZc1e5bgg9n0lkIvewM= =Czt6 -----END PGP SIGNATURE----- --DWffXqb4gEk6GX3kuw0BXBg6TsAW2r9Jv--

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?
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

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

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:
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.
participants (3)
-
David Caro
-
Juan Hernandez
-
Sandro Bonazzola