[opensuse-project] zypper repos (lr)
How about switching default output fields for zypper lr, for the benefit of both help responders, and seekers? Who are the most common users, anyone outside the various support forums? In support forums, it's pretty common that repos are an issue, and when they are, the URIs in those repos are the most vital information. So, why aren't URIs included in the default output? OPs often know they're needed without knowing why, so will include them, but without the -r switch, whereupon someone must ask for them again, with the switch, prolonging the useful response and solution times. OTOH, repo names and nicknames in conjunction with URIs add nothing in this use context. In addition, with both name and alias, and URIs, and default other fields, command output invariably gets wrapped, making their use difficult. Here's mine, unedited: # zypper lr Repository priorities in effect: (See 'zypper lr -P' for details) 72 (raised priority) : 1 repository 90 (raised priority) : 1 repository 99 (default priority) : 10 repositories # | Enabled | GPG Check | URI ---+---------+-----------+----------------------------------------------------------------------------------- 1 | Yes | (r ) Yes | http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Leap_15.3/ 2 | Yes | (r ) Yes | http://opensuse-guide.org/repo/openSUSE_Leap_15.3/ 3 | Yes | (r ) Yes | http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/ 4 | Yes | (r ) Yes | http://ftp5.gwdg.de/pub/opensuse/repositories/multimedia:/apps/openSUSE_Leap... 5 | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/ 6 | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.3/repo/oss/ 7 | Yes | (r ) Yes | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.3/ 8 | Yes | (r ) Yes | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.3/Essentials 9 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/oss/ 10 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/backports/ 11 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/non-oss/ 12 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/sle/ It's the result of repoListColumns = u in my zypper.conf. What information is actually added to URIs by including also either name or alias, much less both? Alternatively, a new switch, appropriate specifically to common help situations, with reduced likelihood of being wrapped, possibly by truncating name and/or alias at some maximum field width, maybe 18, 20 or 24. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2022-04-12 at 19:11 -0400, Felix Miata wrote:
How about switching default output fields for zypper lr, for the benefit of both help responders, and seekers?
Who are the most common users, anyone outside the various support forums?
In support forums, it's pretty common that repos are an issue, and when they are, the URIs in those repos are the most vital information. So, why aren't URIs included in the default output? OPs often know they're needed without knowing why, so will include them, but without the -r switch, whereupon someone must ask for them again, with the switch, prolonging the useful response and solution times. OTOH, repo names and nicknames in conjunction with URIs add nothing in this use context.
A good help responder knows he/she has to ask for "zypper lr --details" the first time, so no time wasted ;-p ...
Alternatively, a new switch, appropriate specifically to common help situations, with reduced likelihood of being wrapped, possibly by truncating name and/or alias at some maximum field width, maybe 18, 20 or 24.
No, the full name and alias are needed. Maybe format the text in a manner that it doesn't wrap (less than 70 chars), being multiline for each entry in some clever way that I do not know how to do ;-) - -- Cheers, Carlos E. R. (from openSUSE 15.3 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYlYOLhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV+b8AnjhOoB3Km8RyuHpc/ne1 IxcBEfXyAJ9ygI/UKn7GuKtlIcNm1op8VeoyoA== =YdR5 -----END PGP SIGNATURE-----
Carlos E. R. composed on 2022-04-13 01:41 (UTC+0200):
No, the full name and alias are needed. For what exactly? I can't think of a single example where a standard name or alias does not replicate a sufficient portion of the URI that the name or alias is no more than bloat.
How often in the name or alias exists anything that isn't evident from the URI, particularly when the information needed is whether a TW repo has been 1-clicked into a Leap installation, or the wrong version of a repo is enabled (e.g. 15.2 mixed with 15.3)? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Carlos E. R. composed on 2022-04-13 01:41 (UTC+0200):
On Tuesday, 2022-04-12 at 19:11 -0400, Felix Miata wrote:
OPs often know they're needed without knowing why,
so will include them, but without the -r switch, whereupon someone must ask for them again, with the switch, prolonging the useful response and solution times.
A good help responder knows he/she has to ask for "zypper lr --details" the first time, so no time wasted ;-p
A plain jane repo list often is not the result of a responder request. Some people search first, and notice the list pastes in the archives, about half of which either haven't followed the command that produced the pasted result ("here are my repos"), or followed commands that didn't show the switch or URI. Appending -r adds the URI, and obfuscatory line wraps, but doesn't eliminate any bloat or redundance. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2022-04-13 02:24, Felix Miata wrote:
Carlos E. R. composed on 2022-04-13 01:41 (UTC+0200):
No, the full name and alias are needed. For what exactly? I can't think of a single example where a standard name or alias does not replicate a sufficient portion of the URI that the name or alias is no more than bloat.
I have seen occasions where the name is wrong, and the name is how the user knows each repo. The alias is used to name the directories used in the local cache.
How often in the name or alias exists anything that isn't evident from the URI, particularly when the information needed is whether a TW repo has been 1-clicked into a Leap installation, or the wrong version of a repo is enabled (e.g. 15.2 mixed with 15.3)?
Depends on each case. I do want the full information for diagnosis. In fact, there are missing fields. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
participants (2)
-
Carlos E. R.
-
Felix Miata