Hi,
On Thu, Apr 07, 2016 at 12:55:40PM +0000, Zbigniew Jędrzejewski-Szmek wrote:
> If you have:
>
> (main package)
> Obsoletes: %{name} < the-new-version-release
>
> %package tc
> Obsoletes: %{name} < the-new-version-release
>
> Both subpackages should get installed on upgrade.
Oh, this is awesome! Exactly what I have been searching for. No idea why
I didn't try make the new base package obsolete the old one.
> Maybe you already thought about this, but I'd add
> Recommends: iproute-tc to the main package, and
I guess that's merely a hint, right?
> Requires: iproute-tc = %{version}-%{release} to tc subpackage.
Why should iproute-tc require itself? Could you please explain the
effect this has?
On Thu, Apr 07, 2016 at 08:07:01AM -0500, Michael Catanzaro wrote:
> This is a good trick; I've had to use it recently. I went with this
> form:
>
> Obsoletes: %{name}%{isa} < the-new-version-release
Hmm. Shouldn't this be '%{?_isa}' instead? At least that's what
https://fedoraproject.org/wiki/PackagingDrafts/ArchSpecificRequires
recommends. Not sure if that is up to date, though.
Thanks, Phil
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
