Feature changed by: Stanislav Brabec (sbrabec) Feature #306304, revision 3 Title: Support "Obsolete this by another package" openSUSE-11.2: New Priority Requester: Desirable Requested by: Stanislav Brabec (sbrabec) Partner organization: openSUSE.org Description: - If third party wants to terminate a temporary branch of a package, - which should is obsoleted by the mainline, adding Obsoletes: foo-old- - branch into the mainline package is not an option (it's possible only - for official packages). + If third party wants to terminate temporary branch of a package, which + should be obsoleted by the mainline, adding Obsoletes: foo-old-branch + into the mainline package is not an option (it's possible only for + official packages). Support for an Obsolete tag counterpart initiated by the existing package would fix this situation. Example: Name: gimp-unstable Version: 2.5.23 Provides: gimp = %{version} ObsoleteBy: gimp >= 2.6 It would allow to provide mainline gimp packages without Obsoletes: - gimp-unstable < 2.6 and even allow thitd partines to create temporary + gimp-unstable < 2.6 and even allow third parties to create temporary branches of packages. Business case (Partner benefit): openSUSE.org: Providing a significantly modified packages, that are - known to be obsolete after upgrade to the + known to be obsolete after upgrade to the next mainline version. Discussion: #1: Andreas Jaeger (a_jaeger) (2009-06-09 15:08:54) Klaus, could you comment on this, please? -- openSUSE Feature: https://features.opensuse.org/306304

Feature changed by: Federico Lucifredi (flucifredi) Feature #306304, revision 5 Title: Support "Obsolete this by another package" openSUSE-11.2: New Priority Requester: Desirable Requested by: Stanislav Brabec (sbrabec) Partner organization: openSUSE.org Description: If third party wants to terminate temporary branch of a package, which should be obsoleted by the mainline, adding Obsoletes: foo-old-branch into the mainline package is not an option (it's possible only for official packages). Support for an Obsolete tag counterpart initiated by the existing package would fix this situation. Example: Name: gimp-unstable Version: 2.5.23 Provides: gimp = %{version} ObsoleteBy: gimp >= 2.6 It would allow to provide mainline gimp packages without Obsoletes: gimp-unstable < 2.6 and even allow third parties to create temporary branches of packages. Business case (Partner benefit): openSUSE.org: Providing a significantly modified packages, that are known to be obsolete after upgrade to the next mainline version. Discussion: #1: Andreas Jaeger (a_jaeger) (2009-06-09 15:08:54) Klaus, could you comment on this, please? #2: Klaus Kämpf (kwk) (2009-06-15 15:27:32) This seems to complete our "reverse dependencies". Michael, your opinion ? + #3: Federico Lucifredi (flucifredi) (2009-06-16 21:49:32) (reply to + #2) + This smells like trouble - RPM compatibility ? + I am not too keen on third parties branching packages, looks like yet- + another-mess... what are the use cases we are looking at solving here? -- openSUSE Feature: https://features.opensuse.org/306304

Feature changed by: Andreas Jaeger (a_jaeger) Feature #306304, revision 8 Title: Support "Obsolete this by another package" - openSUSE-11.2: New + openSUSE-11.2: Rejected by Andreas Jaeger (a_jaeger) + reject date: 2009-08-12 10:17:37 + reject reason: Please discuss upstream - and once it's accepted + upstream, we can do add it. Priority Requester: Desirable Requested by: Stanislav Brabec (sbrabec) Partner organization: openSUSE.org Description: If third party wants to terminate temporary branch of a package, which should be obsoleted by the mainline, adding Obsoletes: foo-old-branch into the mainline package is not an option (it's possible only for official packages). Support for an Obsolete tag counterpart initiated by the existing package would fix this situation. Example: Name: gimp-unstable Version: 2.5.23 Provides: gimp = %{version} ObsoleteBy: gimp >= 2.6 It would allow to provide mainline gimp packages without Obsoletes: gimp-unstable < 2.6 and even allow third parties to create temporary branches of packages. Business case (Partner benefit): openSUSE.org: Providing a significantly modified packages, that are known to be obsolete after upgrade to the next mainline version. Discussion: #1: Andreas Jaeger (a_jaeger) (2009-06-09 15:08:54) Klaus, could you comment on this, please? #2: Klaus Kämpf (kwk) (2009-06-15 15:27:32) This seems to complete our "reverse dependencies". Michael, your opinion ? #3: Federico Lucifredi (flucifredi) (2009-06-16 21:49:32) (reply to #2) This smells like trouble - RPM compatibility ? I am not too keen on third parties branching packages, looks like yet- another-mess... what are the use cases we are looking at solving here? #4: Michael Schröder (mlschroe) (2009-06-17 11:36:55) (reply to #2) Please discuss this first with the upstream rpm-maint list. I strongly against adding this just to our rpm version. (And it should be ObsoletedBy ;-) ) (We could also add a hack to the sat solver so that Provides: obsoletedby(gimp) >= 2.6 or Obsoletes: obsoletedby(gimp) >= 2.6 works, but this is way too ugly for my taste) -- openSUSE Feature: https://features.opensuse.org/306304