Re: depenancy problem: prevent yum from downloading a package I already have
- From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
- Date: Tue, 22 Apr 2008 07:50:34 +0100
Rahul wrote:
Matt Giwer <jull43@xxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:480d6535$0$5738$4c368faf@xxxxxxxxxxxxxx:
Obsolete does not mean useless or that it makes errors.
True. But sometimes one needs features that have only been added to the latest version.
If you can find an rpm of the newest version use yum to install
it with --nogpgcheck and localinstall. I guess if you can create your own rpm
package from what you have installed that would work too.
Thanks Matt! Those are new ideas for me to keep in mind the next time I run into a similar problem (I'm sure I will since pushing the latest stable versions does not seem to be RHEL's forte; I know Fedora is a better alternative but....)
But if you insist, get the original package you installed, let
yum do its thing which will create an installation record. Then reinstall the latest
version.
Another nice idea! Pretty similar to what I did finally.
Yum keeps a record of what it has installed. It does not check
the system for what has been installed by something else.
But why does yum not allow options of the sort:
(1) Allowing the user to tell the yum package manager: I've XXX installed at location yyy.
Well, that's not a yum problem, per se. It's an RPM problem, on which yum is built. And one can, in fact, build a fake, placeholder RPM for just that purpose.
It's just tricky to maintain such packages dependencies. What version of graphical libraries did your binary use? Did its binaries go where required by other tools? Does it have init scripts? What users need to be created? Where does its documentation and configuration files go? When you update it, how do you import old databses to new formats? These aren't such big problems for gnuplot, but for db4 or Apache or MySQL or zlib, it's an adventure.
You can override it, with RPM. Several of us have mentioned the 'yum --downloadonly' option, and the 'rpm -U --force' option.
(2) --ignore the depedancy on package xxx even if *you* (yum) think it is needed and absent.
Not allowing the user to do these things seems to be against the usual Linux assumption that the user knows best what he's asking for (even if he's making a bad coice!)
But, the user *CAN* do these things. It just takes using yum download tools, and using RPM directly!
The lack of such options (in my naiive mind) only seems to tie down a user to a particular package manager. The ability to use yum / rpms / source-makes on a per situation basis wuld seem more pragmatic. I strongly suspect there are implementation issues I'm totally ignorant of though! Just my curiosity.....
I've dealt with this in the past. Yes, RPM does centralize the information, but merging the information is a flipping nightmare without that central control. I think RPM, and Debian's '.deb' format, were written by people with an appreciation for how awkward simply assumeing a component is there can be. Many open source authors make very, very different assumptions about where things belong. (Dan Bernstein, author of qmail and djbdns, comes to mond!) These tools do not play nice with others unless force everyone to work with some sorts of standards: RPM provides many of these standards.
.
- Follow-Ups:
- References:
- Prev by Date: Re: depenancy problem: prevent yum from downloading a package I already have
- Next by Date: Re: depenancy problem: prevent yum from downloading a package I already have
- Previous by thread: Re: depenancy problem: prevent yum from downloading a package I already have
- Next by thread: Re: depenancy problem: prevent yum from downloading a package I already have
- Index(es):
Relevant Pages
|
|
