On Thu, 26 Aug 2004, Robert Vojta wrote: The main thing you have to get right though, is that after you have patched package A n times, an upgrade to a newer full A should remove entries for all the patches to A from the rpm db. The main issue is that patches are not upgrades because no package gets errased when you add a package. An upgrade is always the new package installed followed by the old package erased. Clearly this is not what you want to happen when you add a patch, but when you upgrade to a new full version then rpm must be smart enough to add erase elements to the transaction not only for the earlier major version you are updating but for all the intermediate patches. It could be done, but you would need to find some way in the DB to link the patches to the original package. Just a thought...james _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
