> > > > The attached code implements a plugin that protects against updating > > packages from the Red Hat Network. > > > > It's basically a hacked version of protectbase, and is needed because > on RH > > Enterprise Linux 5 RH use a plugin to present the RH Network channels > as yum > > repositories, so there is no repository configuration file to add a > > protect=1 to in order to allow protectbase to work. > > > > It could be improved upon by implementing a more robust method of > detecting > > that a repository is a RH network repo (currently it relies on > finding the > > text "rhel-" somewhere in the name of the repository. > > > > Thoughts? > > > > why not patch rhn-plugin to be compatible with protectbase? >
I suppose that would be another solution, but I'm not clear what the approach would be. The rhn-plugin has no repo config file in /etc/yum.repos.d, although I suppose one (or several in fact since several channels are presented as repositories) could be created as a dummy config files to include protect=1 in but then yum will probably complain that it can't connect to the repo. Another approach would possibly be to have the rhn-plugin check that protectbase is installed, and then look though other non-protected repos to delete packages from them. Is that the approach you were thinking of? No guarantee that RH would accept the patches though. -- Tony Scholes Beacon Computer Services 82 High Street South Tel: +44(0)1582 478888 DUNSTABLE Beds. Fax: +44(0)1582 478810 LU6 3HD www.beacon.co.uk Beacon Computer Services is a trading name of Caneline Ltd. Registered in England and Wales. Registered No. 1558277. Registered Office: as above.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
