In my opinion, there are two scenarios: (1) the RPM was made by you of an application you wrote yourself or is a third party RPM of a very specific application. In this case, being an application 'off the distribution tree', it will never be upgraded, except when you or the authors write such an upgrade. (2) the application is a regular application, registered as part of the Linux distribution. In this case the chances of it not being upgraded are slim, because most bulk upgrades will find it listed and act accordingly. Theoretically, you could manually upgrade parts of your distribution omitting this one package. However, it will eventually clash with some upgrade affecting a vital library. This could happen in case (1) above as well, except for the simplest applications, since most use shared libraries; you could get away for some time though, by keeping your application using static libraries. Again, this last only with scenario (1). The only way I have found of making software in this condition work is by not upgrading at all. This is the reason why you find some servers with an old distribution and they cannot be upgraded, unless they break free from the 'untouchable' software. Hope this is of use, Gerardo On Tue, Jun 30, 2009 at 10:57 AM, Yuri Csapo<ycsapo@xxxxxxxxx> wrote: > Does anybody know how to instal an RPM on a RH-derived system and make it > persistent so that future upgrades don't replace them? > > -- > Yuri Csapo > Academic Computing & Networking > Colorado School of Mines > CT-256 > Phone: (303) 273-3503 > Fax: (303) 273-3475 > Email: ycsapo@xxxxxxxxx > > Please use the following link to open a service request: > http://helpdesk.mines.edu > =========================================== > With a PC, I always felt limited > by the software available. > On Unix, I am limited only by my knowledge. > --Peter J. Schoenster > -- > To unsubscribe from this list: send the line "unsubscribe linux-admin" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
