7 Jul
2004
7 Jul
'04
21:48
Greets: Yast back in 5.x-8.0 days had this nice feature that would allow for pointing yast to any rpm or archive and designate it as an installation source. For example: I have dl'd the latest beta KDE set to my local ftp server behind my firewall. Point yast to this directory and it always fails and complains that there is no installation source on the medium. Path is correct of course. So was wonder, what the trick is with Yast2 to install remote rpms on mass via yast as it seems to want some sort of inventory on a directory (like the suse.ftp.archive) to make it active. This is burdensome to say the least. So what am I missing. regards /ch