Rember Yast in the old days?
Anybody recall how yast used to allow you to brows an arbitrary file structure looking at rpms? It would tell you if the rpm you were looking at was installed, new than an installed rpm, etc. I believe it would also resolve (or at least indicate) conflicts and dependencies to some extent. That was really nice to have. I expected them to put it back in after they got the QT wrapper finished. It still seems to be missing. There is an option to import a list of rpms from disk, but I have no idea how to form that list. Has anybody worked with this feature? STH
* Steven T. Hatton;
There is an option to import a list of rpms from disk, but I have no idea how to form that list. Has anybody worked with this feature?
/usr/bin/create_package_descr maybe this one -- Togan Muftuoglu | Unofficial SuSE FAQ Maintainer | Please reply to the list; http://susefaq.sf.net | Please don't put me in TO/CC. Nisi defectum, haud refiecendum
On Sat January 24 2004 11:42 am, Steven T. Hatton wrote:
Anybody recall how yast used to allow you to brows an arbitrary file structure looking at rpms? It would tell you if the rpm you were looking at was installed, new than an installed rpm, etc. I believe it would also resolve (or at least indicate) conflicts and dependencies to some extent. That was really nice to have. I expected them to put it back in after they got the QT wrapper finished. It still seems to be missing.
There is an option to import a list of rpms from disk, but I have no idea how to form that list. Has anybody worked with this feature? STH
Mine still does on Suse 9, using a default install and adding additional apps. I was having a problem getting 9 on my desktop and one of the installs using the minumum install yast only listed what was installed during the installation. Any rpms not listed can be found at Suse's download site and can be installed using yast. Rich -- Our lives begin to end the day we become silent about the things that matter. -Martin Luther King- C. Richard Matson
On Saturday 24 January 2004 17:44, C. Richard Matson wrote:
On Sat January 24 2004 11:42 am, Steven T. Hatton wrote:
Anybody recall how yast used to allow you to brows an arbitrary file structure looking at rpms? It would tell you if the rpm you were looking at was installed, new than an installed rpm, etc. I believe it would also resolve (or at least indicate) conflicts and dependencies to some extent. That was really nice to have. I expected them to put it back in after they got the QT wrapper finished. It still seems to be missing.
There is an option to import a list of rpms from disk, but I have no idea how to form that list. Has anybody worked with this feature? STH
Mine still does on Suse 9, using a default install and adding additional apps. I was having a problem getting 9 on my desktop and one of the installs using the minumum install yast only listed what was installed during the installation. Any rpms not listed can be found at Suse's download site and can be installed using yast. Rich -- Our lives begin to end the day we become silent about the things that matter. -Martin Luther King-
C. Richard Matson
Let me give an example. This is actually the reason I asked the question. I just fetched the KDE 3.2 rc1 from a SuSE Mirror. There was a time I could simply point YaST to /download/com/suse/kde/ and see all the rpms, and their status. They didn't even need to be SuSE rpms. I don't believe that is still possible with YaST2. STH
On Saturday 24 January 2004 23:54, Steven T. Hatton wrote:
Let me give an example. This is actually the reason I asked the question. I just fetched the KDE 3.2 rc1 from a SuSE Mirror. There was a time I could simply point YaST to /download/com/suse/kde/ and see all the rpms, and their status. They didn't even need to be SuSE rpms. I don't believe that is still possible with YaST2.
I like to use red carpet for that. Its "mount directory" feature is very useful. Not quite as flexible as the old YaST filesystem browser, but very good nevertheless
* Anders Johansson
On Saturday 24 January 2004 23:54, Steven T. Hatton wrote:
Let me give an example. This is actually the reason I asked the question. I just fetched the KDE 3.2 rc1 from a SuSE Mirror. There was a time I could simply point YaST to /download/com/suse/kde/ and see all the rpms, and their status. They didn't even need to be SuSE rpms. I don't believe that is still possible with YaST2.
I like to use red carpet for that. Its "mount directory" feature is very useful. Not quite as flexible as the old YaST filesystem browser, but very good nevertheless
Midnight Commander is still available, but not really gui .... -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org
On Sat, 24 Jan 2004 19:09:20 -0500
Patrick Shanahan
Midnight Commander is still available, but not really gui ....
That is what I use now and rpm directly from the commandline for batch processing. There is also purp: http://www.lysator.liu.se/purp/ Charles -- "It's God. No, not Richard Stallman, or Linus Torvalds, but God." (By Matt Welsh)
On Sunday 25 January 2004 01:09, Patrick Shanahan wrote:
Midnight Commander is still available, but not really gui ....
... and not really a tool for managing rpms either, unless I've missed a feature. What red carpet lets you do is to "mount" a directory as a "channel". It will then present you with a list of all rpms in that directory that are already installed and available for update, or already installed with the same or newer version. Very handy for mass installations of large numbers of rpms, and extremely useful when you want to install the same rpms on several machines, all running rcd And using the open-carpet tools from open-carpet.org it's very simple to construct your own repository, plus you get access to the repositories constructed for apt4rpm through that site as well (though it seems only for 9.0, it won't do anything that I can see for 8.2) There's even a command line tool. "rug subscribe funktronics" followed by "rug install freevo" for example. No editing of config files necessary A very nifty tool. I only hope now that ximian + suse = true, they integrate it into yast and kill off YOU
Let me give an example. This is actually the reason I asked the question. I just fetched the KDE 3.2 rc1 from a SuSE Mirror. There was a time I could simply point YaST to /download/com/suse/kde/ and see all the rpms, and their status. They didn't even need to be SuSE rpms. I don't believe that is still possible with YaST2.
STH
Thanks for the clarification. I have had the same experience. I remember reading somewhere that yast only works with Suse RPM'S in that regard. Rich -- Our lives begin to end the day we become silent about the things that matter. -Martin Luther King- C. Richard Matson
On 01/25/2004 06:54 AM, Steven T. Hatton wrote:
Let me give an example. This is actually the reason I asked the question. I just fetched the KDE 3.2 rc1 from a SuSE Mirror. There was a time I could simply point YaST to /download/com/suse/kde/ and see all the rpms, and their status. They didn't even need to be SuSE rpms. I don't believe that is still possible with YaST2.
Closest I have seen to the functionality is kpackage. You can configure it to look at a particular directory, and it will tell you if it is new (not installed), or an update (i.e. the rpm in the directory is newer than installed). In some ways it gives more info than Yast 1, but not nearly as fast, especially if there is a large number of rpms in the directory. It does allow for multiple rpm installs (mark, then install marked). It isn't Yast1, but it has met the need. HTH. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
My experience is that kpackage has a is slow, and worse, has very poor flow. It is hard to select your package. And once "installed" almost impossible to find and confirm in the list. On Sat, 2004-01-24 at 23:35, Joe Morris (NTM) wrote:
Closest I have seen to the functionality is kpackage. You can configure
On Tuesday 27 January 2004 07:10, Paul Alfille wrote:
My experience is that kpackage has a is slow, and worse, has very poor flow. It is hard to select your package. And once "installed" almost impossible to find and confirm in the list. Install the package, click on the refresh button (on the left), hit Ctrl+F and type the name of the package (or part of the name is enough). KPackage will find it for you.
-- Kind regards Hans du Plooy hansdp@newingtoncs.co.za
On Sat, 24 Jan 2004 14:44:05 -0800
"C. Richard Matson"
Mine still does on Suse 9, using a default install and adding additional apps.
No what he meant was in the old YaST one can put a whole bunch of RPM's in a local directory, point YaST to them and install them. This feature is not present in YaST2 and I miss it also. Charles -- Linux is obsolete (Andrew Tanenbaum)
participants (9)
-
Anders Johansson -
C. Richard Matson -
Charles Philip Chan -
Hans du Plooy -
Joe Morris (NTM) -
Patrick Shanahan -
Paul Alfille -
Steven T. Hatton -
Togan Muftuoglu