SuSE have had them for a while, the biggest problem IMO is how much they suck in practise. For instance you often want to suggest different packages depending on if you have a KDE or GNOME spin, etc. And given that rpm isn't going to do anything with them, putting them in the package instead of in the repodata. is likely not the best thing to do.
Having them in the package might be better than not having them, maybe.
> > DeltaRPM
> (Looks like this won't be added to rpm yet.)
This is just about where the code lives, and if there can be any code consolidation. deltarpm support has been in Fedora for ~6 months and in SuSE a lot longer, AIUI.
> > New payload format
> Wow, switching from cpio to something else will break a lot of cheezy
> rpm2cpio type scripts.
The summary at sitk.gk2.sk was probably worded badly, however the recent message on the rpm ML makes it clearer that the likely way forward is to have a cpio variant with larger fields ... used only for those rpms that need it.
One obvious benefit being that GNU cpio would also support this larger variant, and thus rpm2cpio would still work for all packages.
> Curious that they do not consider tar an option.
Same reason everyone else hates it, the format itself is horrid and GNU tar doesn't make it look more appealing.
> > Easy way to add or remove autogenerated dependencies
> Debs are built so much differently that there is really no way
> to compare.
Indeed, everything is hard coded. Which works fine if you have an infinite resource of packagers, less so for a company that is paying people to package things.