Re: Overeager cleaning of -devel provides

--047d7ba975c82cc45104e2e47f07
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2013/8/1 Matthew Dawkins <[email protected]>

> So, Virtual provides and creating conflicting provides, still doesn't
> answer the question.
> The multiarch macros deals with installing conflicting files on cross arc=
h
> installs.
>
You don't seem to fully understand what the multiarch policy is about and
that it's not limited to just some rpm macros..
You should read up on it at http://wiki.mandriva.com/en/Policies/Multiarch

Conflicting files is something that would get in the way of having both
libfoo-devel and lib64foo-devel installed, which is why the multiarch stuff
is in place to work around this issue.


> It's wrong b/c what does the number "2" have to do with the package name?
> The api is 2.0 and not 2.
>
Because we don't intend to support building against multiple api versions.
At the time the package was created and the glib2-devel was added as
provides, there was both glib 1 & 2 present and supported for building
against.

As this no longer is the case, sure, a better choice would've been just
'glib-devel' if introduced nowadays,


> If you want to add back some "virtual" provides, why not do it correctly?
> My suggestion is Provides: %{name}%{api} =3D %{EVRD}
>
The actual naming itself, however, isn't really all too important.

--
Regards,
Per =D8yvind

--047d7ba975c82cc45104e2e47f07
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2013/8/1 Matthew Dawkins <span dir=3D"ltr">&lt;<a href=3D"mailto:mattydaw@g=
mail.com" target=3D"_blank">[email protected]</a>&gt;</span><br><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div><div><div>So, Virtual provides and creating conflicti=
ng provides, still doesn&#39;t answer the question.<br></div>The multiarch =
macros deals with installing conflicting files on cross arch installs.=A0</=
div>
</div></div></blockquote><div>You don&#39;t seem to fully understand what t=
he multiarch policy is about and that it&#39;s not limited to just some rpm=
 macros..</div><div>You should read up on it at <a href=3D"http://wiki.mand=
riva.com/en/Policies/Multiarch">http://wiki.mandriva.com/en/Policies/Multia=
rch</a></div>
<div><br></div><div>Conflicting files is something that would get in the wa=
y of having both libfoo-devel and lib64foo-devel installed, which is why th=
e multiarch stuff is in place to work around this issue.</div><div><br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div>
<br></div>It&#39;s wrong b/c what does the number &quot;2&quot; have to do =
with the package name? The api is 2.0 and not 2.<br></div></div></blockquot=
e><div>Because we don&#39;t intend to support building against multiple api=
 versions.</div>
<div>At the time the package was created and the glib2-devel was added as p=
rovides, there was both glib 1 &amp; 2 present and supported for building a=
gainst.</div><div><br></div><div>As this no longer is the case, sure, a bet=
ter choice would&#39;ve been just &#39;glib-devel&#39; if introduced nowada=
ys,</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><br></d=
iv>If you want to add back some &quot;virtual&quot; provides, why not do it=
 correctly? My suggestion is Provides: %{name}%{api} =3D %{EVRD}<br>
</div></blockquote><div>The actual naming itself, however, isn&#39;t really=
 all too important.</div><div><br></div><div>--</div><div>Regards,</div><di=
v>Per =D8yvind</div></div>

--047d7ba975c82cc45104e2e47f07--