[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: .spec file for multiple target distros
- From: Jeff Johnson <n3npq jbj gmail com>
- To: RPM Package Manager <rpm-list redhat com>
- Subject: Re: .spec file for multiple target distros
- Date: Mon, 31 Jul 2006 07:46:22 -0400
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jul 30, 2006, at 5:23 AM, Axel Thimm wrote:
Don't abuse disttags for that, that's what upsets Jeff (and he's right
about that).
Actually, using %{dist} to include gfortran (or not) isn't what upsets.
The feebleness of the bleary fog of multiple conflicting attempts to
overload substrings
in Release: with admonishments aand advocacy to encourage use of %
{dist} and other
signifiers when there are other and better ways.
One final hint:
We seem to agree that everything but %{dist} in EVR is identical.
Since %{dist} is the least significant part of EVR comparison, the use
during install is as a tie-breaker.
Which means that
%{?dist:Disttag: %{dist}}
syntax, (perhaps injected into all spec files *without change* by
overloading
%description as a macro rather than a section marker), and
some rather simple code in rpm to use RPMTAG_DISTTAG as
a tie-breaker if it exists, would seem to achieve the intended
result much more effectively than trying to convince everyone to
incorporate
Release: 1.2.3.4.5.foo.bar.%{dist}
as their packaging style.
Heck, you can even do it both ways ...
73 de Jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEze2buHNkGyA5spERAjEzAKDnTrfXoutcZqh1TJCy11lqM8NELQCfXBN+
4VkRNiKEvvATmdNt12weojY=
=ljla
-----END PGP SIGNATURE-----
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]