On Friday 11 March 2005 18:38, Ingo Strauch wrote:
On Thu, 10 Mar 2005 20:08:56 -0500
Geoffrey <esoteric@3times25.net> wrote:
Yast will work on a console as well. It doesn't make sense to use a non-standard app (apt) to update your packages on Suse. It won't keep your rpm database properly updated.
Now you got me curious. Apt will use the same RPM files as Yast and underneath will use the same rpm executable to install them. How should that lead to differences or even a not properly updated rpm database? Or did I miss something?
But I agree that yast shouldn't be too difficult either. The trick as you said is simply typing a name to the search field and see what comes up.
Cheers, Ingo Thanks for the opinions. I am gaining a lot from you guys.
I switched off and logged in as root and run up Yast as you suggested. I put emacs (and again with xemacs) into the search box as suggested. Yast displayed, in RHS window, all modules installed, with a tick in each check box. So, as a test, I unticked the -el- module and clicked "Accept". Took some time, but it eventually un-installed this module. Then I repeated the search and got a list of the installed modules, with check boxes ticked; but no sign of any module ( eg -el- ) available for installation. I did fiddle with the 'filter' but couldn't get Yast to display any 'available' software, just the software already installed. This is why I turned to rpm in the first place. Am I supposed to do something special to get such a list displayed? From Konqueror I have triggered a Yast installation; Yast started up, whirred a bit, but it never installed anything. I tried this with/without DVD in drive.