It becomes a quick decent into dependancy hell. The easiest in my view is to either play the rpm game and let your vendor do all the heavy lifting. Update a package when they do, etc. The other option is compile everything from source and handle everything yourself.
> -----Original Message----- > From: Aria Bamdad [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 18, 2004 8:39 AM > To: [EMAIL PROTECTED] > Subject: Re: RPM question > > > So then if you do want to install a package using RPM that would need > another package that was installed manually, you would have to use the > --nodeps option to force the install? > > For example, I had to install MySQL using the source. To do > this, I had to > uninstall the older RPM installed version and other apps that > used it because > they were dependent on it. Now, I have to re-install those > 'other apps' that > depend on MySQL but RPM doesn't know about the new MySQL install. > > > On Wed, 18 Feb 2004 08:37:48 -0600 Ryan Ware said: > >I don't believe you can. RPM only manages RPM's. > > > >> -----Original Message----- > >> From: Aria Bamdad [mailto:[EMAIL PROTECTED] > >> Sent: Wednesday, February 18, 2004 8:34 AM > >> To: [EMAIL PROTECTED] > >> Subject: RPM question > >> > >> > >> Hi, > >> > >> If I install a package using the configure/make method, how > >> do I tell RPM > >> that the package is installed so that it will know about it? > >> > >> Thanks. > >> >
