Naive, newbie question concerning installs to a Suse system
I've got a freshly-installed Suse 10 system. (Eval) There are a few things I want to add to the system (lineakd, lame, Opera 8.5, among others). I've been slowly learning more about Linux for a few years now, and for the last couple of years have been messing around with Suse 9.0 and Suse 9.1. My impression is that if I want to maintain the usability of Yast and RPM in general, I have to do all of my installs through them. In other words, if I choose to do an install manually somehow, like rpm from the command-line, Yast will no longer know what's what and will become undependable. If I install something via a script, or recompile something in to the kernel myself, than RPM won't have an accurate database and will be unusable. Is this a valid concern, or are the experienced among you shaking your heads and laughing at my ignorance? Thanks, Steve
On Sat, 2005-10-22 at 18:16 -0400, Steve Jacobs wrote:
I've got a freshly-installed Suse 10 system. (Eval)
There are a few things I want to add to the system (lineakd, lame, Opera 8.5, among others).
I've been slowly learning more about Linux for a few years now, and for the last couple of years have been messing around with Suse 9.0 and Suse 9.1.
My impression is that if I want to maintain the usability of Yast and RPM in general, I have to do all of my installs through them. In other words, if I choose to do an install manually somehow, like rpm from the command-line, Yast will no longer know what's what and will become undependable.
Not true. YaST uses the same RPM data base as the command line rpm.
If I install something via a script, or recompile something in to the kernel myself, than RPM won't have an accurate database and will be unusable.
Just keep in mind that the same rpm database is used for any rpm based operation.
Is this a valid concern, or are the experienced among you shaking your heads and laughing at my ignorance?
Thanks, Steve -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On 22 Oct 2005, stevetjacobs@gmail.com wrote:
In other words, if I choose to do an install manually somehow, like rpm from the command-line, Yast will no longer know what's what and will become undependable.
No, you can install rpm's from the command line. YaST uses the rpm database.
If I install something via a script, or recompile something in to the kernel myself, than RPM won't have an accurate database and will be unusable.
Use checkinstall: http://checkinstall.izto.org/ which is included with SUSE. Charles -- LILO, you've got me on my knees! (from David Black, dblack@pilot.njin.net, with apologies to Derek and the Dominos, and Werner Almsberger)
On Saturday 22 October 2005 15:36, Charles philip Chan wrote:
On 22 Oct 2005, stevetjacobs@gmail.com wrote:
In other words, if I choose to do an install manually somehow, like rpm from the command-line, Yast will no longer know what's what and will become undependable.
No, you can install rpm's from the command line. YaST uses the rpm database.
If I install something via a script, or recompile something in to the kernel myself, than RPM won't have an accurate database and will be unusable.
Use checkinstall:
which is included with SUSE.
That looks cool. However, I didn't find it in YaST. The website does have a binary RPM. I simply downloaded it and double-clicked it. It installed just fine. HOWEVER... It gives me a "command not found" when I try to actually run it. I even rebooted to see. Typing "which checkinstall" doesn't do anything either. -- kai www.perfectreign.com linux - genuine windows replacement part
On 22 Oct 2005, kai@perfectreign.com wrote:
That looks cool. However, I didn't find it in YaST.
It is on DVD 1 (Group: Development/Tools/Building): http://www.novell.com/products/linuxpackages/professional/checkinstall.html Charles -- "Nature abhors a Vacuum" -- Brian Behlendorf on OSS (Open Sources, 1999 O'Reilly and Associates)
On 22 Oct 2005, kai@perfectreign.com wrote:
HOWEVER... It gives me a "command not found" when I try to actually run it. I even rebooted to see. Typing "which checkinstall" doesn't do anything either.
If you really want to use the package on the website add, make sure /usr/local/bin, and /usr/local/sbin is in root's path. Also, make sure /usr/local/lib is in /etc/ld.so.conf (which it should be). If not add it and run ldconfig. Charles -- printk ("Kicking board.\n"); linux-2.6.6/drivers/net/lp486e.c
Kai, On Saturday 22 October 2005 15:53, Kai Ponte wrote:
... It installed just fine.
HOWEVER... It gives me a "command not found" when I try to actually run it. I even rebooted to see. Typing "which checkinstall" doesn't do anything either.
It's installed into /usr/sbin. You need to put that directory into your PATH environment variable if you don't want to have to type "/usr/sbin/checkinstall" each time you run it.
-- kai
Randall Schulz
Kai Ponte wrote:
On Saturday 22 October 2005 15:36, Charles philip Chan wrote:
On 22 Oct 2005, stevetjacobs@gmail.com wrote:
In other words, if I choose to do an install manually somehow, like rpm from the command-line, Yast will no longer know what's what and will become undependable. No, you can install rpm's from the command line. YaST uses the rpm database.
If I install something via a script, or recompile something in to the kernel myself, than RPM won't have an accurate database and will be unusable. Use checkinstall:
which is included with SUSE.
That looks cool. However, I didn't find it in YaST. The website does have a binary RPM. I simply downloaded it and double-clicked it. It installed just fine.
HOWEVER... It gives me a "command not found" when I try to actually run it. I even rebooted to see. Typing "which checkinstall" doesn't do anything either.
You can check where the stuff is installed e.g "rpm -ql checkinstall",
"rpm -qpl
My impression is that if I want to maintain the usability of Yast and RPM in general, I have to do all of my installs through them. This was already answered to some extent. Just one additional comment about installing software. For the most part, if you install a package using RPM (either via YaST or RPM) that package is maintained in the RPM database. However, there is no problem if you want to install software using tarballs. The main concern here is that when installing from tarballs,
On Saturday 22 October 2005 6:16 pm, Steve Jacobs wrote:
those packages are not in the RPM database.
(Note that you can build an RPM from a tarball).
The main concern with installing software outside of RPM is that RPM does
not know about it, and you need to be careful if you install the same
package with RPM at a later time.
--
Jerry Feldman
participants (7)
-
Charles philip Chan -
Jerry Feldman -
Kai Ponte -
Ken Schneider -
Randall R Schulz -
Sid Boyce -
Steve Jacobs