Ann, For a distribution that is maintained by RPM, such as Red Hat and SuSE, you _should_ maintain everything with RPM, unless you're installing a package that is not provided by the distributor. Even then you might want to consider creating your own spec files and use RPM to build and install it.
There are a couple of ways to make this process easier. One is the up2date facility that Adam was reporting a problem on earlier today. Alan Cox also talked about a port of apt-get to handle RPM files. Take a look at http://apt-rpm.tuxfamily.org. Mark Post -----Original Message----- From: Ann Smith [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 13, 2002 2:27 PM To: [EMAIL PROTECTED] Subject: RPM's and TAR's (was PREREQ's) We're still trying to install the prereq's for the JDK 1.3.0. We have gotten past our initial 'cannot install' package problem. It ended up the Hummingbird(Exceed) was warping the binary ftp transfer of the rpm file. But we still have an issue with determining everything needed for glibc. rpm -qR glibc-2.1.2-4.s390.rpm gives the response: /sbin/ldconfig not too helpful When we attempt to install glibc we get messages regarding many conflicts. The developer site just says we need glibc 2.1 or newer. So we went looking for an rpm file. I am not sure we really can always avoid tarz files but rpm's seemed to be available for glibc. I guess my question is - (1) Is it normal to attempt installs and deal with the conflicts as they are indicated or being a newbie am I missing some rpm query options that would help me out?(2) Do the SUSE maintenance CD's (if you have maintenance contract) always have rpm files or are tarz files normal maintenance practice (just part of life, learn to deal with it)?
