[Engine-devel] Feedback requested on name change
This is a multi-part message in MIME format. --------------090408020509030405010906 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit We have now separated tools repositories which are built independently from ovirt-engine, for example "ovirt-image-uploader". Our rpms (ovirt-engine) has a dependency on those tools, using the following option: <snip> ... Requires: %{name}-image-uploader ... <snip> %{name} is substituted by 'ovirt-engine' during build, creating a dependency on "*ovirt-engine-image-uploader*". This, in turn, makes a non-resolved dependency, as the actual package name built for image-uploader is "*ovirt-image-uploader*". We can resolve this by either changing the dependency in our rpms or by changing the tools package names (relevant also for iso-uploader and log-collector). Please let me know which way seems preferable for this. Thanks. -- Alex Lourie. --------------090408020509030405010906 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> We have now separated tools repositories which are built independently from ovirt-engine, for example "ovirt-image-uploader". Our rpms (ovirt-engine) has a dependency on those tools, using the following option:<br> <br> <snip><br> ...<br> Requires: %{name}-image-uploader<br> ...<br> <snip><br> <br> %{name} is substituted by 'ovirt-engine' during build, creating a dependency on "<b>ovirt-engine-image-uploader</b>". This, in turn, makes a non-resolved dependency, as the actual package name built for image-uploader is "<b>ovirt-image-uploader</b>".<br> <br> We can resolve this by either changing the dependency in our rpms or by changing the tools package names (relevant also for iso-uploader and log-collector).<br> <br> Please let me know which way seems preferable for this.<br> <br> Thanks.<br> <br> <pre class="moz-signature" cols="72">-- Alex Lourie.</pre> </body> </html> --------------090408020509030405010906--
On 05/17/2012 02:01 PM, Alex Lourie wrote:
We have now separated tools repositories which are built independently from ovirt-engine, for example "ovirt-image-uploader". Our rpms (ovirt-engine) has a dependency on those tools, using the following option:
<snip> ... Requires: %{name}-image-uploader ... <snip>
%{name} is substituted by 'ovirt-engine' during build, creating a dependency on "*ovirt-engine-image-uploader*". This, in turn, makes a non-resolved dependency, as the actual package name built for image-uploader is "*ovirt-image-uploader*".
We can resolve this by either changing the dependency in our rpms or by changing the tools package names (relevant also for iso-uploader and log-collector).
Please let me know which way seems preferable for this.
I like more the new shorter package names. In addition they reflect better the fact that they are not subpackages of the engine. But take into account that changing the names means that the upgrade path has to be managed carefully. The new renamed packages should obsolete the old ones. I would also suggest to replace the "Requires: %{name}-whatever" that we currently use with "Requires: %{name}-whatever = %{version}-%{release}".
participants (2)
-
Alex Lourie -
Juan Hernandez