On Mon, Sep 23, 2002 at 03:28:04PM -0500, Dave Ihnat wrote:
> Still, if I had a pristine, only-from-RPMs system, I might decide to take
> the plunge without discussion and do an update from 6.2 -> 7.3--except.
> There are a fair number of software packages that, due to the age of
> the system and the number of dependencies, simply couldn't be updated
> from stock RPMs and so were compiled and installed using the (package)
> native installation procedures. Apache, SSH, and OpenSSL to name a few,
> but there are a number of others, too.
>
> How well or poorly have people found RH update to work in such a system?
What rpm is based on is the version number and the provides/requires
information. If you played by the rules, you should be okay. If,
however, you used a Red Hat version numbering system and your version is
older than Red Hat's, your package will likely be updated.
What you should typically do is to not use the native installation
procedures. Download a Red Hat source rpm, install the source, then go
in and change the source tar file, update the spec file, and build.
Then you'll have the right info in the right places.
I think that you're currently in the situation where Red Hat does not
know that you've got Apache, SSH, or OpenSSL even installed (how could
it, if they're not in the rpm database?). If you try to install another
package that has one of them as dependencies, the packages will need to
be re-installed.
If I was in your shoes, I'd back the system up, do a clean install, and
then re-apply the customizations. Yeah, that sucks...
.../Ed
--
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]
Member #1, Red Hat Community Ambassador Program
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
