I wonder how the EXTRA_PROV files is being made, that is required by create_package_descr? Another thing I would like to know is why the information is actually needed by create_package_descr or is it YPM that needs this information? How does the information influence the behaviour of YPM?
I understand that it could be needed as e.g: # rpm -q --whatprovides /bin/sh bash-2.05b-96
bug the other way around does not work: # rpm -q --provides bash (I would expect /bin/sh here)
Is EXTRA_PROV made manually?
Also in 9.1 the rpm kdebase3-SuSE provides an EXTRA_PROV too. This one and the one in suse/setup/description are rather different. Is this intended?
Why not use the Provides tag in the rpm to store this information and use that?? It would be easy for suse rpm contributors to support this too => Would that make it easier to provide yast enabled rpm repositories?
Here is what I do ... /srv/ftp/9.1 is my root dir
create_package_descr \ -d /srv/ftp/9.1/suse \ -l english \ -x /srv/ftp/9.1/suse/setup/descr/EXTRA_PROV \ -o /srv/ftp/9.1/suse/setup/descr
groetjes ..
Richard Bos wrote:
I wonder how the EXTRA_PROV files is being made, that is required by create_package_descr? Another thing I would like to know is why the information is actually needed by create_package_descr or is it YPM that needs this information? How does the information influence the behaviour of YPM?
I understand that it could be needed as e.g: # rpm -q --whatprovides /bin/sh bash-2.05b-96
bug the other way around does not work: # rpm -q --provides bash (I would expect /bin/sh here)
Is EXTRA_PROV made manually?
Also in 9.1 the rpm kdebase3-SuSE provides an EXTRA_PROV too. This one and the one in suse/setup/description are rather different. Is this intended?
Why not use the Provides tag in the rpm to store this information and use that?? It would be easy for suse rpm contributors to support this too => Would that make it easier to provide yast enabled rpm repositories?
Op dinsdag 8 juni 2004 21:56, schreef Richard Bos:
I wonder how the EXTRA_PROV files is being made, that is required by create_package_descr? Another thing I would like to know is why the information is actually needed by create_package_descr or is it YPM that needs this information? How does the information influence the behaviour of YPM?
I understand that it could be needed as e.g: # rpm -q --whatprovides /bin/sh bash-2.05b-96
bug the other way around does not work: # rpm -q --provides bash (I would expect /bin/sh here)
Is EXTRA_PROV made manually?
Also in 9.1 the rpm kdebase3-SuSE provides an EXTRA_PROV too. This one and the one in suse/setup/description are rather different. Is this intended?
Why not use the Provides tag in the rpm to store this information and use that?? It would be easy for suse rpm contributors to support this too => Would that make it easier to provide yast enabled rpm repositories?
No one?? Something else and related: is there a script to create the file content (ftp.suse.com/suse/i386/9.1/content)?
Perhaps there is a howto explaining what YOU needs to access a remote (3rd party) rpm repository, like: ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1/yast-source $ ls content directory.yast media.1 suse
On Wednesday 09 June 2004 22:21, Richard Bos wrote:
Perhaps there is a howto explaining what YOU needs to access a remote (3rd party) rpm repository, like: ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1/yast-source $ ls content directory.yast media.1 suse
Have a look at ftp.suse.com/suse/people/kraxel.
He made several YaST repositories in that directory. Seems not too difficult. And perhaps you could ask him: kraxel at bytesex dot org.
Cheers,
Leen
On Wed, Jun 09, 2004 at 10:21:39PM +0200, Richard Bos wrote:
No one?? Something else and related: is there a script to create the file content (ftp.suse.com/suse/i386/9.1/content)?
Perhaps there is a howto explaining what YOU needs to access a remote (3rd party) rpm repository, like: ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1/yast-source $ ls content directory.yast media.1 suse
See the docs here:
/usr/share/doc/packages/yast2-packagemanager /usr/share/doc/packages/yast2-online-update
autoinstall@lists.opensuse.org
-
Grant Williamson -
Leendert Meyer -
Martin Vidner -
Richard Bos