|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
In regard to: Packaging a new version of a core perl module, Matt Grimm...:
How does one go about packaging an RPM for a newer version of a core perl module? The core modules are all included in the perl RPM, so they can't simply be replaced as with non-core modules. If the new files will conflict with the older ones, I'm not sure how to work around that.
The short answer is that there's no easy way to work around the issue. We've seen it too. About all you can do is use --replacefiles when you install the RPM, to replace the files in the original package. The down-side is that if you use some kind of automatic update facility (like Red Hat NetWork) for vendor packages, then unless you take special precautions, the next time your vendor releases an updated version of perl, it could overwrite your version. Last In "wins". Your only other option is to override how the perl module installs itselfat package build time, so that it goes into site_perl or some other directory, and then make certain that any modules that "use foo" get your version
first, rather than the older version that's part of core perl. Also not easy. Tim -- Tim Mooney mooney@xxxxxxxxxxxxxxxxxxxxxxxxx Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxxxxx http://lists.rpm.org/mailman/listinfo/rpm-list