Project

General

Profile

Actions

Bug #5491

closed

Misleading naming in applications/zypperPackageManagerSettings/1.0

Added by Florian Heigl about 10 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
3
Assignee:
-
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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...";
Actions

Also available in: Atom PDF