-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 29, 2006, at 11:36 AM, Axel Thimm wrote:
The probable reason for the request (can't guess the OP's motivation, but it very much looks so) is to ensure proper upgrade paths within "fc" when rebuilding the same src.rpm package on different releases of the distro, which is a very handy method to support/maintain several releases with one specfile, and which has spread all over the repos by now.
Widespread usage does not insure problems are resolved. Guaranteeing upgradeability on a per-distro basis by configuring Release: through manually administered policies is intrinsically doomed as well. Hint: Try exposing a web-counter that is shared cooperatively between different build systems. That is easier engineering than discussing rpm EVR comparison schemes until hell freezes over. Wouldn't be hard at all to add options to express, say, I want a Release that is newer than latest in repo1 but older than next chosen for repo1. where the web-counter thingy maintains Release: state persistently. 73 de Jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEy4RduHNkGyA5spERAmsqAKCP/evzIJNPmWHhiBc2GouFrsAArACg6166 C10T2HCCTXI8XldEGA5vO5k= =3WxQ -----END PGP SIGNATURE----- _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list