Re: [suse-autoinstall] Adding custom RPMs to an NFS install setup
Richard Bos wrote:
I'm doing it differently using suse-8.2, that I'll explain below. In my case everytime after I run create_package_descr I need to refresh the installed source by deleting and adding the source using yast that points to my autoinstall source. That's because the cache /var/adm/YaST/InstSrcManager is not updated with the info/files created by create_package_descr. Am I doing something wrong or is it a bug?
Neither, this is the way it should go. If you put some packages on system and use the script, it does not imply that you also want to use the source for the running system., unless its the same version of course, you might need to do it.
My update method in short: a update directory mirrors some directories from ftp.suse.com renamed the suse dir to base created a new dir called latest linked this dir (latest) so suse a script now links in the most recent packages from the update and base directories into the latest directory (right format). After that the create_package_descr is called.
Yast should actually be able to take the latest version if the same package exists with 2 versions. But this is not clean anyways. Anas
On Thursday 10 July 2003 14:37, Anas Nashif wrote:
Richard Bos wrote:
I'm doing it differently using suse-8.2, that I'll explain below. In my case everytime after I run create_package_descr I need to refresh the installed source by deleting and adding the source using yast that points to my autoinstall source. That's because the cache /var/adm/YaST/InstSrcManager is not updated with the info/files created by create_package_descr. Am I doing something wrong or is it a bug?
Neither, this is the way it should go. If you put some packages on system and use the script, it does not imply that you also want to use the source for the running system., unless its the same version of course, you might need to do it.
Well, I'm running autoyast on a SuSE-8.2 system. The Yast Package Manager (YPM) would be allowed by me to use the repository that is created by create_package_descr. But that is not the point I'm a little confused by the way autoyast interacts with YPM when selecting additional packages. Is my assumption correct that for autoinstall "yast -> change source of installation" must be used to tell autoyast were it can find the package repository?? If yes, that would indeed mix the autoinstall pkg repository with the operational pkg repository. I'm doing it this way as I don't another way to do it. If there is another way could you explain how (or refer to the docu)?
My update method in short: a update directory mirrors some directories from ftp.suse.com renamed the suse dir to base created a new dir called latest linked this dir (latest) so suse a script now links in the most recent packages from the update and base directories into the latest directory (right format). After that the create_package_descr is called.
Yast should actually be able to take the latest version if the same package exists with 2 versions. But this is not clean anyways.
Ah, good to know. -- Richard Bos Without a home the journey is endless
participants (2)
-
Anas Nashif -
Richard Bos