Home_greyopenFATE - openSUSE feature tracking > #305930
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Don't increase version number if not strictly needed

Feature state



As I use KDE42 and other newer packages I often do a factory update. I see that the footprint is very big. Because a package gets always rebuild when for instance a dependent library get rebuild. Even if the package is 100% the same it'll gets the same version number.
If possible I would like to have binary identical packages to keep the same version number this reduces bandwidth usage for users/mirrors and it can give people a false feeling that Linux is buggy "as so many packages need to be updated".


icons/user_comment.png V. P. wrote: (8 years ago)

Yes. Maybe yast or zypper can provide an option to ignore the package release version number change and only update the packages that have a major/minor package version change.

In yast there is a menu item "package->all in this list->update only if newer package is available". Two new items could be added: "update only if major version change" and "update only if minor version change", both would ignore the release version number change.

icons/user_comment.png P. R. wrote: (8 years ago)

This behaviour would much more cause problems that it actually solves. It should be fixed in the way the description says.

icons/user_comment.png A. J. wrote: (8 years ago)

Coolo, I think this is solved differently for factory, now. Could you provide details, please?

icons/user_comment.png A. S. wrote: (8 years ago)

The only solution here is to not build packages if not needed. If we build them and build others against, but just not publish all of them we will be in big trouble due to all kind of inconsistencies.

This is partly solved meanwhile via the "no change" detection after building a package and comparing it to the former one. This is active when building for 11.2 and Factory.

Other/Further concepts are thinkable, but need a more specific description on what base the "not needed to build" decision should happen.

Last change: 8 years ago
Score: 3
  • Negative: 0
  • Neutral: 1
  • Positive: 3
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint