Crusher-1:/home/crrey # rpm -Fhv rpm: no packages given for install: A rather expected response. One has to know the package to update and hence back to the orignal frustration!
So I guess what your saying is that I have to go through every package and see if it will update? Original dilemma, How does one know if and when a package or list of packages has been updated by the developer?
So let's see: rpm -qv kdemultimedia3 rpm -qv kdelibs3 rpm -qv kdeartwork3 rpm -qv koffice rpm -qv kartsbuilder rpm -qv kpackage rpm -qv kpat rpm -qv ksysguard rpm -qv kugar rpm -qv lisa rpm -qv ktalkd rpm -qv xmms rpm -qv moneydance rpm -qv kappdock rpm -qv kec rpm -qv there are 113 files in the KDE/updates_for_8.0/applications directory alone, 13 in the base directory, 32 in the development directory. Then we have the SaX2, 3ddaig, commercial dirs and everything from a1 to zq1 in the updates. Granted the YOU reads the /update/8.0 files, however it has (and in fact just recently) omits packages from time to time that I could update visually and "quickly" compare against my system to see and compare the files be a simple highlight and "F2" button. So therefore we find ourselves spending an inordinant amount of time to do something that was previously a rather simplified task.
Hey, I'm all for innovations and moving forward. However, as and end-user and fanatically loyal SuSE patriot I find the lastest changes irksome and tedious.
Just MHO, Curtis
On Thursday 02 May 2002 02:39 pm, Marcel Broekman wrote:
Thanks Tor,
Subject: Re: [SLE] Ok, this sucks! Date: Thu, 2 May 2002 18:13:16 +0000 From: Tor Sigurdsson
To: marcel@ietsmet.nl Ever heard of "rpm -F" ?
It updates the package if and only IF
o It is already installed and o It is newer than the already installed package
rpm -Fhv *.rpm <-- updates everything that HAS to be updated, and nothing else.
Yes i know this! That said, i don't consider myself an rpm expert but you're forgetting that this thread is mostly about missing the ease of use of installing new, updated and individual packages, a function that Yast1 had and Yast2 doesn't. Before we can do what you suggest we'd still have to know which packages to download, then download and hope all dependencies are met (Yast1 didn't do this, i know). And run SuSEconfig afterwards. This is where apt-get could step in beautifully i think. It's here and ready, so why not use it and expand the possibilities.
cheers, Marcel
- -tosi
---snip---
getting apt-get to do the basic updating stuff is quite easy and won't cost you much time. Now if only SuSE could join the development of this great app and build their update, upgrade and install mechanism around it, preferably with a nice GUI plugin/module in Yast, they'd have the best package management tool in the world!
For those from SuSE that monitor the list post. Please inform the Product development department of these concerns. The feature I mentioned in YaST1 is sorely missed.
Respectfully, Curtis
ditto, Marcel A module for yast2 with the same functionality as Ximian's RedCarpet would
On Thursday 02 May 2002 13:31, Curtis Rey wrote: probably satisfy most peoples needs. Building it on top of apt4rpm would make a great package management and update utility. This is an area where mandrake has done pretty well with urpmi and the mandrake software manager. Throw in the cooker servers and Mandrake has a pretty useful and reliable update utility. If suse had something like this.....