[openFATE 305930] Don't increase version number if not strictly needed
Feature added by: Joop Boonen (worldcitizen) Feature #305930, revision 1, last change by Title: Don't increase version number if not strictly needed Buildservice: Unconfirmed Priority Requester: Important Requested by: Joop Boonen (worldcitizen) Description: 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 yo 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". -- openSUSE Feature: https://features.opensuse.org/305930
Feature changed by: Vincent Petry (PVince81) Feature #305930, revision 3 Title: Don't increase version number if not strictly needed Buildservice: Unconfirmed Priority Requester: Important Requested by: Joop Boonen (worldcitizen) Description: 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 yo 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". + Discussion: + #1: Vincent Petry (pvince81) (2009-06-30 16:27:55) + 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. -- openSUSE Feature: https://features.opensuse.org/305930
Feature changed by: Pavol Rusnak (prusnak) Feature #305930, revision 5 Title: Don't increase version number if not strictly needed Buildservice: Unconfirmed Priority Requester: Important Requested by: Joop Boonen (worldcitizen) Description: 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 yo 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". Discussion: #1: Vincent Petry (pvince81) (2009-06-30 16:27:55) 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. + #2: Pavol Rusnak (prusnak) (2009-07-02 02:57:44) (reply to #1) + This behaviour would much more cause problems that it actually solves. + It should be fixed in the way the description says. -- openSUSE Feature: https://features.opensuse.org/305930
Feature changed by: Andreas Jaeger (a_jaeger) Feature #305930, revision 6 Title: Don't increase version number if not strictly needed - Buildservice: Unconfirmed + Buildservice: Evaluation Priority Requester: Important Requested by: Joop Boonen (worldcitizen) Description: 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 yo keep the + 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". Discussion: #1: Vincent Petry (pvince81) (2009-06-30 16:27:55) 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. #2: Pavol Rusnak (prusnak) (2009-07-02 02:57:44) (reply to #1) This behaviour would much more cause problems that it actually solves. It should be fixed in the way the description says. + #3: Andreas Jaeger (a_jaeger) (2009-07-09 16:55:46) + Coolo, I think this is solved differently for factory, now. Could you + provide details, please? -- openSUSE Feature: https://features.opensuse.org/305930
Feature changed by: Adrian Schröter (adrianSuSE) Feature #305930, revision 7 Title: Don't increase version number if not strictly needed - Buildservice: Evaluation + Buildservice: Done Priority Requester: Important Requested by: Joop Boonen (worldcitizen) Description: 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". Discussion: #1: Vincent Petry (pvince81) (2009-06-30 16:27:55) 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. #2: Pavol Rusnak (prusnak) (2009-07-02 02:57:44) (reply to #1) This behaviour would much more cause problems that it actually solves. It should be fixed in the way the description says. #3: Andreas Jaeger (a_jaeger) (2009-07-09 16:55:46) Coolo, I think this is solved differently for factory, now. Could you provide details, please? + #4: Adrian Schröter (adriansuse) (2010-02-20 10:46:50) + 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. -- openSUSE Feature: https://features.opensuse.org/305930
participants (1)
-
fate_noreply@suse.de