RE: building a package that can not be upgraded

["Hebenstreit, Michael" <michael.hebenstreit@xxxxxxxxx>]

We have a complex driver package – which is in beta, but already used (aka tested) by a lot of people. Something is not working cleanly, rpm –F fails with an cpio error, and so a temporary workaround is needed.

 

%prep was my solution vector, but I wondered if there was an alternative – like a flag “this package can not be upgraded”

 

Thanks

Michael

 

From: rpm-list-bounces@xxxxxxxxxxxxx [mailto:rpm-list-bounces@xxxxxxxxxxxxx] On Behalf Of Valery Reznic
Sent: Thursday, July 05, 2012 2:10 PM
To: General discussion about the RPM package manager
Subject: Re: building a package that can not be upgraded

 

You can write pre-install script that check number of installed package instances ($1, iirc) and if

package already installed, then exit with error message and non-zero status.

 

But why do you want to do such a thing?

 

Valery

 

---

From: "Hebenstreit, Michael" <michael.hebenstreit@xxxxxxxxx>
To: "rpm-list@xxxxxxxxxxxxx" <rpm-list@xxxxxxxxxxxxx>
Sent: Thursday, July 5, 2012 8:17 PM
Subject: building a package that can not be upgraded

Is there an easy way to create a package that throws an error when trying to upgrade? Aka rpm -i should work, rpm -F/-U should not


Thanks
Michael

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list