Adam Williamson wrote:
> Huh - that's handy, and I did not actually know --nopostun (something
> new every day, etc.). It does involve including instructions on how to
> find the package, though, which would inevitably go stale as it moves
> from u-t to stable. Still, thanks.
Seeing how this is not the first time a broken %postun script causes
unfixable trouble with updating a package, I think RPM really needs a way
for a new version of a package to override the old version's %postun. It
would be similar to how triggers work, but it should run INSTEAD OF the
original %postun, not in addition to it. (As I understand it, postun
triggers unfortunately run in addition to normal %postun.)
Kevin Kofler
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
