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
On Wednesday 07 July 2004 21:48, chris h wrote:
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.
To install the latest KDE from SuSE, add http://ftp.gwdg.de/pub/suse/i386/supplementary/KDE/update_for_9.1/yast-sourc... as another source. Be sure to move it above the base source so that it takes precedence. Such a directory that can be a YaST source directory does not always exist. Cheers, Leen
On July 7, 2004 04:31 pm, Leendert Meyer wrote:
Such a directory that can be a YaST source directory does not always exist.
Tks...a bit of a misunderstanding. By source I meant a data source for yast. Guess this feature did not survive into the new Yast as in its previous incarnation you could point yast to any ftp server (local or remote) and use that server as an medium for yast. ie: you could use yast to identify and install rpm from anywhere. This feature seems to be limited now to yast integration on Kongi but the limitation is one rpm at a time. For example: I have a local ftp server on another machine on my network and I want to instruct Yast to use it as an installation source/medium. Its a collection of various rpms. There is no way that I have found to have yast accept this directory as an "installation medium" as it wont stop whining that its not an install source. Regards /ch
On Wednesday 07 July 2004 22:39, chris h wrote:
On July 7, 2004 04:31 pm, Leendert Meyer wrote:
Such a directory that can be a YaST source directory does not always exist.
Tks...a bit of a misunderstanding.
Really? With source I do not mean *.src.rpm, but a source of rpm's, the *.i586.rpm's and alike. But scroll down.
By source I meant a data source for yast. Guess this feature did not survive into the new Yast as in its previous incarnation you could point yast to any ftp server (local or remote) and use that server as an medium for yast. ie: you could use yast to identify and install rpm from anywhere. This feature seems to be limited now to yast integration on Kongi but the limitation is one rpm at a time.
For example: I have a local ftp server on another machine on my network and I want to instruct Yast to use it as an installation source/medium. Its a collection of various rpms. There is no way that I have found to have yast accept this directory as an "installation medium" as it wont stop whining that its not an install source.
YaST -> Software -> Change Source of Installation There. Change what? Yes, change /source/ of installation. ;) There you can add another BASE source directory, either local (HD) or remote (ftp, http, nfs, samba). Also there you can add /extra/ source directory, as I already described in the case of KDE. But these directories are not just "a bunch of rpm's". They have to meet certain criteria, as you can see if you browse the KDE example in my previous mail. Cheers, Leen
On July 7, 2004 05:17 pm, Leendert Meyer wrote:
But these directories are not just "a bunch of rpm's". They have to meet certain criteria, as you can see if you browse the KDE example in my previous mail.
Yup thats the difference between old and new. The old version of yast could be pointed to any ftp directory and it would register the URL as a source and allow for installation. Dependency checks varied of course. This seems to be no longer the case with the current shipping version which is a shame to some degree as it was such a time saver..;) Thanks for your help on this, its appreciated. /ch
On Thursday 08 July 2004 03.21, chris h wrote:
On July 7, 2004 05:17 pm, Leendert Meyer wrote:
But these directories are not just "a bunch of rpm's". They have to meet certain criteria, as you can see if you browse the KDE example in my previous mail.
Yup thats the difference between old and new. The old version of yast could be pointed to any ftp directory and it would register the URL as a source and allow for installation. Dependency checks varied of course. This seems to be no longer the case with the current shipping version which is a shame to some degree as it was such a time saver..;)
I use red carpet for this. I used to use lufs (http://lufs.sourceforge.net) to mount the ftp server as a directory and then use red carpet to update from that directory. Haven't looked at lufs in a while though, and now that I do, it looks abandoned. I hope there is an alternative, because that was useful
I don't know if I'm following the list correctly, but I think the only diference is that the new yast requires BOTH sources. That in the old one, you "replace" SUSE sources with an FTP... In the new one, you define BOTH. It works better, now since it can find the dependancies from the CD... As example, I've downloaded and Installed FwBuilder. by downloading the varios *.rpm to a directory, Added the director to Yast as a new source, and then did search for Firewall... Jerry On Thu, 2004-07-08 at 03:21, chris h wrote:
On July 7, 2004 05:17 pm, Leendert Meyer wrote:
But these directories are not just "a bunch of rpm's". They have to meet certain criteria, as you can see if you browse the KDE example in my previous mail.
Yup thats the difference between old and new. The old version of yast could be pointed to any ftp directory and it would register the URL as a source and allow for installation. Dependency checks varied of course. This seems to be no longer the case with the current shipping version which is a shame to some degree as it was such a time saver..;)
Thanks for your help on this, its appreciated.
/ch
On July 8, 2004 03:42 am, Jerome R. Westrick wrote:
As example, I've downloaded and Installed FwBuilder. by downloading the varios *.rpm to a directory, Added the director to Yast as a new source, and then did search for Firewall...
Sure that works. What used to work is to point Yast to the ftp server directly..:) so there was no need to download to local dir then point yast to local dir. Now you cannot do that any more as far as I can tell and it requires that extra step. Also, is harder to script and automate...thats the real issue..:) /ch
participants (4)
-
Anders Johansson -
chris h -
Jerome R. Westrick -
Leendert Meyer