coreutils installation and RPM management
Hi, I was trying to install MySQL as an RPM when KManager (I think it was - I'm remote at an internet cafe') told me coreutils was a needed dependency.
I ran KManager independently and it showed coreutils in my installed column. duh! I downloaded coreutils-5.2.1 and configured and make'd everything. Then I 'make install'd (to default path (Turned out to be '/usr/local/bin')) My original coreutils are located in '/bin'. Now, I have some updated coreutils in the new location ('/usr/local/bin') What do I do now? I know I should probably re- 'make install --exec-prefix=PATH' to '/bin' - such as: 'make install --exec-prefix=/bin' Will I bork anything doing this? Why didn't KManager correctly detecte a default install of coreutils on 'Slackware 10.0'? As an aside, will installing via source not update the rpm management software and, therefore, not detect when an even newer coreutils (or whatever) is installed? Thanks in advance. Carl C |
Quote:
In response to the second, because Slackware doesn't use RPM. Slackware uses Slackpackages. Go to LinuxPackages.net to download packages. You will find that the dependancies for MySQL are already satisfied on a base Slack install, and that the Slack package will probably work fine. |
Slackpackages, eh?
OK. Home now.
Slackpackages, huh? Ok, thanks. I'll look it up. FYI: Also, I ran the 'which' command from the . dir and it informs me that everything is pointing to '/usr/local/bin'. Guess I'll see what happens over time. Thanks for the info on the slackpackages, again. |
Just for the records, MySQL comes with Slackware by default, if you did a full install it's already installed.
|
Yup, I knew MySQL was installed. I wanted to install a newer version. I had already installed, via source build (in a different dir than the existing, vanilla-install copy), MySQL 4.1 but it was nagging at me that there was another install location on the disk.
I've been reading "MySQL in a Nutshell" by O'Reilly and they suggestted the use of an RPM. I thought, "Why Not. I've never used RPM before anyway." Thanks to killerbob, now I know why. heh! Anyway, I used KManager to un-install MySQL then I backed up the entire MySQL Directory of the source build I made and tried the RPM usage and now, here we are. OH, Why didn't I start that logbook like so many sites said I should have? :tisk: |
In future, if you want to upgrade a package to the new version, use "upgradepkg".
Say the original package is something innocuous, like "xfce-4.2.0-i486-3.tgz". That's actually the XFCE base package from Slack 10.1. Now, I want to upgrade it to "xfce-4.2.2-i486-1.tgz", which is the version in Slack-current. In order to upgrade, I do not need to first uninstall my existing xfce. Instead, I download the new package, and install it with "upgradepkg xfce-4.2.2-i486-1.tgz". upgradepkg will install the new package, overwriting everything, and then check the install log against the list of files added by the original package. It then removes any files that were in the original package, but are not in the new one. This makes it really easy and really quick to upgrade a package. :) |
Re: coreutils installation and RPM management
Quote:
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var Also if you keep your "compile" directory (where you ran ./configure, make, and make install) and you "bork" something when you install it, sometimes you can cd back to the "compile" directory and type "make uninstall" (or something similar read the README or INSTALL file) and it will uninstall the files (for the most part). The best way to handle software management is by using slackpacks. Then, as another poster said, you can use upgradepkg, installpkg, and removepkg to take care of all your software. Later, MMYoung |
Re: Re: coreutils installation and RPM management
Quote:
Quote:
Quote:
Thanks MMYoung and killerbob, Carl ------------------------------------ Disclaimer--->Boring stuff below *They're all connected together via a WRT54G(wired - the wireless is for my LT. The WRT54G is locked down tight using AES, IP Filtering and no default p/w's + other junk). My servers serve webpages; though, I'm still trying to get Samba set up and working. They're test machines so I can learn.:study: To get on the net at home I use my mother's computer running a 56k Modem (I live in the stone ages). I have to run to the local Internet cafe' to download the truely massive stuff - you know, greater than 6 Meg - so I'm kind of limited in how fast I can get things done. I'll usually wait until I need more than a few files so I can grab all the files at once instead of just grabbing a few at a time. |
No problem, glad to help. If you want a good guide to creating your own slackpacks you can find all kinds of really good information from LinuxPackages. They have several HOWTO's on their site that I used to learn "how to" make packages the RIGHT way. You could also use checkinstall but it is no longer included on the Slackware CD's (at least it ain't on my CD's from Slackware). You would have to download it from HERE.
Later, MMYoung |
All times are GMT -5. The time now is 02:13 AM. |