Re: Install time expansion of macros

["Christian Goetze" <cg hq addamark com>]

> However, there's been almost no need for install system expansion, your
> example is trivially solved by expansion on build using
>     %define VERSION 1.1

Not if I don't have my build system available, or, for whatever reason,
cannot easily reproduce the build environment for that particular version.
In  particular, if I am the customer of a binary only RPM, I am stuck
unless I am willing to manually unpack and repack the rpm.

> pkgadd is different model, rpm has no concept of "patched", only rebuild
> with "newer" version. rpm also has much richer set of metadata than
> pkgadd, so there's little reason (jmho) to abuse version with "patched"
> suffix, a changelog is far more descriptive.

Actually, in my example "real" or "orig" would be better. The idea is you
have an installation that cannot be stopped or uninstalled or otherwise
touched, which claims to be version X of my system, but isn't (for
whatever reason). I would like to install the correct, real version X but
cannot do that without --relocate.

In my case here, I will probably be able to get away with --relocate, but
don't like it that much, since it means that just about everything will
need to have a common prefix...
--
cg