Bug #5491
closed
Misleading naming in applications/zypperPackageManagerSettings/1.0
Added by Florian Heigl about 10 years ago.
Updated over 7 years ago.
Description
There is one option that is described as:
<DESCRIPTION>Also add the corresponding source repositories</DESCRIPTION>
Everyone I had try configure a rule thought it would auto-add a second repo for the SRPMs by some url magick.
Instead it means, that the source for this repository will be added.
Personally I fell for this twice. So it's reproducible. It would be great if the text could be a bit changed.
What I also don't understand is the idea behind this option.
Maybe you could extend the help for this selection to describe when you would want to click "no".
Don't understand when someone sets up zypper repos in this directive and then selects "don't add them".
resulting message will be from this one from zypperPackageManagerSettings.st
!zypper_repositories_edit::
"@zypperPackageManagerSettings
@result_success@${zypper_uuid[${zypper_index}]}
@Repository@${zypper_name[${zypper_index}]}
@${g.execRun}##${g.uuid}@#The source ${zypper_name[${zypper_index}]} will NOT be added as the repository addition parameter is off in the Policy Instance. Skipping...";
- Description updated (diff)
- Status changed from New to 8
- Assignee set to Matthieu CERDA
- Priority changed from N/A to 3
- Target version set to 2.6.18
I agree with this. It needs to be clarified.
- Status changed from 8 to Discussion
This Technique needs major cleaning / refactoring ...
I suggest that it is either:
- splitted in two parts:
- One to manage Zypper itself
- One to manage Zypper repositories
- Adapted to be like the APT management one, but I think that maybe having several techniques to manage package managers and then a generic repository addition one would be the way to go in this case :)
- Assignee deleted (
Matthieu CERDA)
- Target version changed from 2.6.18 to 2.6.19
- Target version changed from 2.6.19 to 2.6.20
- Assignee set to Matthieu CERDA
- Target version changed from 2.6.20 to 2.10.10
Matthieu, please handle that one. Anything better than what is actually done will be a progress.
- Target version changed from 2.10.10 to 2.10.11
- Target version changed from 2.10.11 to 2.10.12
- Target version changed from 2.10.12 to 2.10.13
- Target version changed from 2.10.13 to 2.10.14
- Target version changed from 2.10.14 to 2.10.15
- Target version changed from 2.10.15 to 2.10.16
- Target version changed from 2.10.16 to 2.10.17
- Target version changed from 2.10.17 to 2.10.18
- Target version changed from 2.10.18 to 2.10.19
- Target version changed from 2.10.19 to 2.10.20
- Target version changed from 2.10.20 to 277
- Target version changed from 277 to 2.11.18
- Target version changed from 2.11.18 to 2.11.19
- Target version changed from 2.11.19 to 2.11.20
- Target version changed from 2.11.20 to 2.11.21
- Target version changed from 2.11.21 to 2.11.22
- Target version changed from 2.11.22 to 2.11.23
- Target version changed from 2.11.23 to 2.11.24
- Target version changed from 2.11.24 to 308
- Target version changed from 308 to 3.1.14
- Target version changed from 3.1.14 to 3.1.15
- Target version changed from 3.1.15 to 3.1.16
- Target version changed from 3.1.16 to 3.1.17
- Assignee deleted (
Matthieu CERDA)
- Target version changed from 3.1.17 to 3.1.18
- Target version changed from 3.1.18 to 3.1.19
- Status changed from Discussion to Rejected
This is not the case anymore
Also available in: Atom
PDF