Mailinglist Archive: opensuse-autoinstall (47 mails)

[Eric Whiting <ewhiting@xxxxxxxx>]

Thorsten/Anas,

Has there been any more changes or activity on these concepts?
http://lists.suse.com/archive/suse-autoinstall/2002-Aug/0043.html

Patching a clean 8.0 NFS install tree with files from
ftp.anywhere.com:/*/suse/i386/update/8.0/
is not a straight forward matter, yet it would greatly simplify
installs. I'd much rather just do a NFS install and be done rather than
have to go back and run YOU.

2 ways to do this were mentioned. I have a few questions:

===Option 1 -- this option was to overwrite rpm files with the new
'fixed' one.

In the 8.0 updates tree I can see the following sysconfig updates:

 sysconfig-0.23.14-54.i386.patch.rpm
 sysconfig-0.23.14-54.i386.rpm
 sysconfig-0.23.14-54.i386_de.info
 sysconfig-0.23.14-54.i386_en.info
 

In the tree from the suse 8.0 DVD I see this file:

 sysconfig-0.23.14-30.i386.rpm

In this case I assume I could just take sysconfig-0.23.14-54.i386.rpm
and overwrite the sysconfig-0.23.14-30.i386.rpm file.

Do I need to do anything with the .patch and .info files?

I can write a short perl script to do this.

===Option 2 -- this option involved copied the updates (which ones? all
or just the main .rpm file?) This also means you must remove the 'old'
package that is being replace right? 

The makeCommon.sh script needs to generate a new common.pkd file. I
tried this on my clean suse 8.0 tree and it generated a common.pkd file
that seemed quite different from the file originally in the
suse/setup/descr tree... How critical is the format of that file? The
size field is different. Other things seem different as well.

Is there a 'new/improved' way to build the common.pkd file? Or is the
specific not that critical? I was able to get a common.pkd file that
looks mostly ok.

Thanks,
eric