>>>>> "KP" == Kamil Paral <kparal@xxxxxxxxxx> writes: KP> I wonder why nobody responded. Is something unclear? Well, fundamentally I don't think this has much to do with the mechanics of packaging. Fedora has an existing updates policy, drawn up by FESCo, at https://fedoraproject.org/wiki/Updates_Policy. I don't think having something on the same topic but saying something different and dictated by a different committee is productive. If there's some specific statement of just _how_ someone should package something in order to support updating across two versions, then that's a reasonable thing to put in the packaging guidelines. (Yes, there might be stuff in the guidelines now which probably doesn't meet this criterion; that's no reason to add more.) I can't think of any general rule, though. Current the guidelines don't have much to say about updates; they discuss scriptlets and how they can tell if they're being run as part of an update (as opposed to a fresh installation). They talk about %changelog entries that you make when updating something, and mention the inclusion of CVE info when making security updates. There's information about updates of packages requiring bootstrapping with prebuilt content. There's nothing about _when_ to push updates. - J< -- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/packaging@xxxxxxxxxxxxxxxxxxxxxxx
