Feature changed by: Adrian Schröter (adrianSuSE) Feature #308835, revision 2 Title: performance: no-ABI-change flag - Buildservice: New + Buildservice: Rejected by (adrianSuSE) + reject date: 2010-01-21 12:18:29 + reject reason: as written in last comment Priority Requester: Mandatory Requested by: Michael Meeks (michael_meeks) Partner organization: openSUSE.org Description: When submitting a package, for which we know there has been no ABI change - eg. we changed only a manual page, or where we wrote the patch ourselves and are certain - it should be possible to 'osc commit' with a flag set; such that this package will be re-built, but no dependent packages will be triggered. This is particularly key for things like glibc / hal and lower stack things, that have ABIs that ~never change incompatibly - yet lots of things depend on. Business case (Partner benefit): openSUSE.org: This would substantially accelerate repository builds, and increase the time for which they are stable. + Discussion: + #1: Adrian Schröter (adriansuse) (2010-01-21 12:18:17) + an abi change is not enough to avoid rebuild triggering. a header file + might change anyway or the pure existins of some files can have an + influence to others. you never know what other packages are using from + your package. + however, we have a feature to validate ABI as qa check for updates. -- openSUSE Feature: https://features.opensuse.org/308835