[New: openFATE 310454] Warn when disabling publish when dependent repositories exist
Feature added by: Will Stephenson (wstephenson) Feature #310454, revision 1 Title: Warn when disabling publish when dependent repositories exist Buildservice: Unconfirmed Priority Requester: Important Requested by: Will Stephenson (wstephenson) Description: eg disabling publish in KDE:Distro:Factory should warn that the dependent repositories in KDE:Unstable:Playground that build using the results of KDE:Distro:Factory will continue to publish. This can lead to subtle runtime incompatibilities when users install packages built vs a newer version of kdelibs than they have installed, or unresolvable packages in the published dependent repos at best. -- openSUSE Feature: https://features.opensuse.org/310454
Feature changed by: Todd R (TheBlackCat) Feature #310454, revision 2 Title: Warn when disabling publish when dependent repositories exist Buildservice: Unconfirmed Priority Requester: Important Requested by: Will Stephenson (wstephenson) Description: eg disabling publish in KDE:Distro:Factory should warn that the dependent repositories in KDE:Unstable:Playground that build using the results of KDE:Distro:Factory will continue to publish. This can lead to subtle runtime incompatibilities when users install packages built vs a newer version of kdelibs than they have installed, or unresolvable packages in the published dependent repos at best. + Discussion: + #1: Todd R (theblackcat) (2010-08-30 19:13:35) + Wouldn't it be better if we could just set the flags for a repository + to automatically follow the flags for the repository it depends on? + + Currently you can set a global option (explicitly enabled or explicitly + disable) for build, publish, debuginfo, and use for build for a + project. The settings for each repository in that project can then be + set to either inheret that setting or override it to something + else. Perhaps in addition to explicitly enable, explicitly disable, or + inheret from the project, there was a third option to inherent that + setting from the parent repository (I am not sure the proper name, I + mean the repository the project's repository is built against). + + As an example, if you set KDE:Unstable:Playground:openSUSE_11. + 3_KDE_Distro_Factory to inheret its settings, when you disable + publishing on KDE:Distro:Factory/openSUSE_11.3, publshing of KDE: + Unstable:Playground:openSUSE_11.3_KDE_Distro_Factory is automatically + disabled as well. You would, of course, still be able to override it, + but doing it automatically would make things easier for packagers and + reduce the chances of annoying mistakes occuring. -- openSUSE Feature: https://features.opensuse.org/310454
Feature changed by: Lukas Krejza (gryffus) Feature #310454, revision 3 Title: Warn when disabling publish when dependent repositories exist Buildservice: Unconfirmed Priority Requester: Important Requested by: Will Stephenson (wstephenson) Partner organization: openSUSE.org Description: eg disabling publish in KDE:Distro:Factory should warn that the dependent repositories in KDE:Unstable:Playground that build using the results of KDE:Distro:Factory will continue to publish. This can lead to subtle runtime incompatibilities when users install packages built vs a newer version of kdelibs than they have installed, or unresolvable packages in the published dependent repos at best. Discussion: #1: Todd R (theblackcat) (2010-08-30 19:13:35) Wouldn't it be better if we could just set the flags for a repository to automatically follow the flags for the repository it depends on? Currently you can set a global option (explicitly enabled or explicitly disable) for build, publish, debuginfo, and use for build for a project. The settings for each repository in that project can then be set to either inheret that setting or override it to something else. Perhaps in addition to explicitly enable, explicitly disable, or inheret from the project, there was a third option to inherent that setting from the parent repository (I am not sure the proper name, I mean the repository the project's repository is built against). As an example, if you set KDE:Unstable:Playground:openSUSE_11. 3_KDE_Distro_Factory to inheret its settings, when you disable publishing on KDE:Distro:Factory/openSUSE_11.3, publshing of KDE: Unstable:Playground:openSUSE_11.3_KDE_Distro_Factory is automatically disabled as well. You would, of course, still be able to override it, but doing it automatically would make things easier for packagers and reduce the chances of annoying mistakes occuring. + #2: Lukas Krejza (gryffus) (2011-09-05 16:26:08) + This feature will improve stability of opensuse a lot! Please include + it... -- openSUSE Feature: https://features.opensuse.org/310454
Feature changed by: Andreas Jaeger (a_jaeger) Feature #310454, revision 4 Title: Warn when disabling publish when dependent repositories exist - Buildservice: Unconfirmed + Buildservice: New Priority Requester: Important Requested by: Will Stephenson (wstephenson) Partner organization: openSUSE.org Description: eg disabling publish in KDE:Distro:Factory should warn that the dependent repositories in KDE:Unstable:Playground that build using the - results of KDE:Distro:Factory will continue to publish. + results of KDE:Distro:Factory will continue to publish. This can lead to subtle runtime incompatibilities when users install packages built vs a newer version of kdelibs than they have installed, or unresolvable packages in the published dependent repos at best. Discussion: #1: Todd R (theblackcat) (2010-08-30 19:13:35) Wouldn't it be better if we could just set the flags for a repository to automatically follow the flags for the repository it depends on? - Currently you can set a global option (explicitly enabled or explicitly disable) for build, publish, debuginfo, and use for build for a project. The settings for each repository in that project can then be set to either inheret that setting or override it to something else. Perhaps in addition to explicitly enable, explicitly disable, or inheret from the project, there was a third option to inherent that setting from the parent repository (I am not sure the proper name, I mean the repository the project's repository is built against). - As an example, if you set KDE:Unstable:Playground:openSUSE_11. 3_KDE_Distro_Factory to inheret its settings, when you disable publishing on KDE:Distro:Factory/openSUSE_11.3, publshing of KDE: Unstable:Playground:openSUSE_11.3_KDE_Distro_Factory is automatically disabled as well. You would, of course, still be able to override it, but doing it automatically would make things easier for packagers and reduce the chances of annoying mistakes occuring. #2: Lukas Krejza (gryffus) (2011-09-05 16:26:08) This feature will improve stability of opensuse a lot! Please include it... -- openSUSE Feature: https://features.opensuse.org/310454
participants (1)
-
fate_noreply@suse.de