[Engine-devel] Separating engine-setup from ovirt-engine

[Ofer Schreiber]

----- Original Message -----
> On 07/03/2012 10:23 PM, Dan Kenigsberg wrote:
> > On Tue, Jul 03, 2012 at 06:20:43PM +0300, Michal Skrivanek wrote:
> >> On Jul 3, 2012, at 16:53 , Juan Hernandez wrote:
> >>
> >>> On 07/03/2012 03:43 PM, Ofer Schreiber wrote:
> >>>> In our days, ovirt-engine-setup is a part of the big
> >>>> ovirt-engine rpm.
> >>>> This means that each time you need to build yourself a new
> >>>> ovirt-engine-setup rpm, you need to compile all the engine.
> >
> > Could this possibly be avoided by an optional flag to the build
> > script?
> 
> indeed.
> or make rpm after 'cd packaging' would only build the packaging, or
> configure script on what to build, etc.

1. the "cd packaging" option is possible, but it means we will have another Makefile and spec file inside the packaging dir, just for engine-setup.
This will actually separate engine-setup rpm from the ovirt-engine base rpm, and will require the same release-cycle/versioning/etc as Dan stated.
Doing this will just save us the external git, as it will have to be a separate package, just inside the same git

2. configure script is fine, but as long as we're a sub-package of ovirt-engine, we will have to build the engine every time we want to build the setup.

> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>