Yast is an rpm based system so if you installed a new program using rpm -i , yast will know about it. If you install it using (compile, make, install) from tarball - yast will not know about it. Nor will any other package managers such as apt-for-suse etc. If you want yast to know about the tarball installations do ./configure make checkinstall checkinstall will create a rpm - which you can then install using rpm -i. In this case, yast will know about this program. Note that the quality of the rpms created with checkinstall is debatable but it should be ok for most simple applications. Osho On Wed, 27 Oct 2004 20:41:02 +0200, Paul wrote:

If I install a program from a tar (compile,make,install) or an rpm with rpm -i, how can I let YaST know that the programs are installed?

Thank You Paul Ryan

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

*** Reply to message from Paul on Wed, 27 Oct 2004 20:41:02 +0200 One more candle and a trip around the Sun***

If I install a program from a tar (compile,make,install) or an rpm with rpm -i, how can I let YaST know that the programs are installed?

you can run /sbin/SuSEconfig after you install everything by hand... it updates the databases and links that Suse looks at for finding your program . Only problem now is to get everyone to FINALLY decide where these "user" installed programs should go... so they can have the right links to the libraries and anything else they may need to actually run .... /sbin/SuSEconfig is what YAST runs after each update , install of new software or install of rpm package using yast or YAST ( never quite certain which of those that ought to be...) Now if you want to get really crazy add re-carpet to the mix ( you need to run the /sbin/SuSEconfig command when you finish installing anything w / red-carpet, in order to keep the database strait.. -- j -- nemo me impune lacessit