Yepper, that's stuff I was worried about. It looks like the INDEX.gz file is easily recreatable and all the MD5SUMS should be easily fixed up. The main one that I'm concerned about is the ARCHIVES.gz. If it's not used by YAST then, I should just be able to ignore it.
You know of any other files that might be a concern? Leland > -----Original Message----- > From: Post, Mark K [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 27, 2003 4:57 PM > To: [EMAIL PROTECTED] > Subject: Re: Merge SuSE updates and original CDs??? > > > Leland, > > If you've ever looked closely, the "real" rpm files have names like: > aaa_base.rpm > cpio.rpm > gdbm.rpm > m4.rpm > ps.rpm > texinfo.rpm > > If you replaced those with _identically_ named updates, > you'll might be > fine, but note that there are other files, other places in > the CD that have > information such as the size of the packages, and dependency > information. > If that metadata changes enough between versions of a > package, you might > have real problems during/after the installation. > > > Mark Post > > -----Original Message----- > From: Lucius, Leland [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 27, 2003 5:38 PM > To: [EMAIL PROTECTED] > Subject: Merge SuSE updates and original CDs??? > > > Anyone know how to merge downloaded SLES8 updates back onto > the original CD > images or into an FTP tree? It can't be as simple as > replacing the older > versions of the RPMs, can it? > > Thanks, > > Leland >
