Feature changed by: Sven Burmeister (rabauke) Feature #306957, revision 3 Title: Allow ymp (one-click installs) to set the repo priority openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Sven Burmeister (rabauke) Description: When people use one-click installs to e.g. install or update KDE4, they get a lot of dependency issues because the buildservice repo does not have the right priority, i.e. higher than e.g. the oss or update repository. One-click installs only make sense if they are easy to use and facilitate the process of adding a repo. Having to open YaST software management to adjust the priority manually and re-running the update afterwards is not "one-click". Setting-up a repo includes setting the correct priority. The problem with ymp setting repos' priority is that those are relative to the repos already installed. The best solution would be to read the other repos' priority and suggest priorities for the new repos accordingly. The user can still change them in the one-click GUI. The minimal solution would be to just allow the user to set the repo's priority via the one-click GUI. Discussion: #1: Jan Engelhardt (jengelh) (2009-08-06 14:25:12) This would be a race between the priorities set in my own system vs. the ones ymp uses. + #2: Sven Burmeister (rabauke) (2009-08-06 18:31:27) (reply to #1) + A race? + Two scenarios: + 1. The added repo does not exist yet. How can there be a race? + 2. The added repo does already exist. The user decides which priority + to change it to (if that is possible at all, AFIAK currently it would + just add a second one). No problem either. +   +   -- openSUSE Feature: https://features.opensuse.org/306957

Feature changed by: Andreas Jaeger (a_jaeger) Feature #306957, revision 6 Title: Allow ymp (one-click installs) to set the repo priority - openSUSE-11.2: Unconfirmed + openSUSE-11.2: Rejected by Andreas Jaeger (a_jaeger) + reject date: 2010-11-15 10:29:45 + reject reason: Not done in time for openSUSE 11.2. Priority Requester: Desirable Requested by: Sven Burmeister (rabauke) Description: When people use one-click installs to e.g. install or update KDE4, they get a lot of dependency issues because the buildservice repo does not have the right priority, i.e. higher than e.g. the oss or update repository. One-click installs only make sense if they are easy to use and facilitate the process of adding a repo. Having to open YaST software management to adjust the priority manually and re-running the update afterwards is not "one-click". Setting-up a repo includes setting the correct priority. The problem with ymp setting repos' priority is that those are relative to the repos already installed. The best solution would be to read the other repos' priority and suggest priorities for the new repos accordingly. The user can still change them in the one-click GUI. The minimal solution would be to just allow the user to set the repo's priority via the one-click GUI. -   Edit: To clarify, this is not about automatic changes, it is about ymp checking e.g. oss and update repo's priority, decreasing the number by one and proposing that priority to the user who has to accept it. If e.g. oss was set to 100 and update to 99, ymp would propose 98 for the new repo.  Discussion: #1: Jan Engelhardt (jengelh) (2009-08-06 14:25:12) This would be a race between the priorities set in my own system vs. the ones ymp uses. #2: Sven Burmeister (rabauke) (2009-08-06 18:31:27) (reply to #1) A race? Two scenarios: 1. The added repo does not exist yet. How can there be a race? 2. The added repo does already exist. The user decides which priority to change it to (if that is possible at all, AFIAK currently it would just add a second one). No problem either. -   -   -- openSUSE Feature: https://features.opensuse.org/306957