I was told by a guy who doesn't work here anymore that using the Epoch:
keyword with a high number will stop a package from a repo from
overwriting your rpm, like if you use:
Epoch: 10000
This only works if you are building your own rpms so you can insert that
in the spec file. Highest Epoch wins, and any non-zero Epoch wins over a
missing Epoch. Kinda messed up way of doing it I guess but it works. It
isn't locked though. Not sure how that could be done.
I may have misunderstood what it is you are trying to do...
Cheers,
Gary Gatling | ITECS Systems
On Thu, 2 Sep 2010, Kinzel, David wrote:
Of course, that doesn't prevent a 'rpm -U' from updating it... :)
Kevin
Unless you get really creative, and build the package with some
%pretrans requirements that need a trigger file to be set, before it
proceeds. Or anything else equally ridiculous as that. :)
This email communication and any files transmitted with it may contain
confidential and or proprietary information and is provided for the use of the
intended recipient only. Any review, retransmission or dissemination of this
information by anyone other than the intended recipient is prohibited. If you
receive this email in error, please contact the sender and delete this
communication and any copies immediately. Thank you.
http://www.encana.com
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list