https://bugzilla.novell.com/show_bug.cgi?id=373167 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=373167#c8 --- Comment #8 from Elmar Stellnberger (AT/K) <estellnb@gmail.com> 2008-04-02 23:25:31 MST ---
(In reply to comment #4 from Elmar Stellnberger (AT/K)) I am not sure what the alias column is supposed to be good for at all. The repository is identified by alias (or by number or URI) in the *repo commands and --repo options - it is essential.
It is somewhat clear that YaST will need an internal identifier to join its own data with and to maintain the identifyability of a repo after renaming or changes to the URI (f.e. to employ another mirror), but please call this one id, ident or somehow else. No data base designer will ever join towards a column called name.
It should not be displayed by default. Instead I would expect the URI to be displayed as by rug. The text console is somewhat limited when it comes to readability, many users _complained_ about the URI displayed by default. I would go for -u option to display URIs as it is not that essential. First you need to know what repositories you have defined so that you can manipulate them. If you need to know their exact location for whatever purpose you will invoke zypper repos with -u or -a.
For sure I have experienced the same problem. Nevertheless the basic problem is not that the URI is displayed. It does not seldomly provide useful information not only in case of an ambiguously named repository(that for we basically desire a rename), but also for the case that the user needs the URI like when it comes to open the repository by a browser, to check for the response time of the server, whether it is reachable at all or to whois it. The basic problem is for sure that all columns together are broader than the with of the text console, which causes line wraps and the content to be almost illegible. That is why I have added the following to my bashrc: :: alias rug='rug --no-abbrev' It will crop the URI before it can exceed the line, reveal as much as possible of it(usually still enough to open a browser quickly) and more important that reveals the server in use. So that is in a fact a matter of overlonglyness or line excessions respectively.
Regardless of that re**name** is for sure supposed to change the name not the alias. Well not. Although i agree it's confusing. Maybe we should drop the renamerepo command and add --alias and --name options to the modifyrepo command.
Now what else? What you supposed to be the alias should become the name. What you supposed to be the name is in deed an internal identifier the user is not interested in at all. Drop the id-column out!! It worsens the problem of overlong columns. No unnecessary information ought to be displayed here. And the URI should be cropped where the line ends - as already argued.
last but not least: Reordering the repo-list at the zypper commandline as well as for the YaST user interface (though this is an indpendent issue in regards to renaming) is for my mind best to be provided by the same command as renaming. Stating the positional number where the repo should show up in the repo list is that way the best solution to provide a directive for reordering - simply put the positional number in place of the name identifier. What would that be good for? What about adding an aption to the repos command to sort by alias, name and priority, or even URI? IMO adding means to manually assign unique numbers to the repositories in order to sort them is >meaningless.
That would possibly deserve its own discussion. * Assigning priorities is for sure no bad idea. * Nevertheless that will just provide limited means to sort the repos. * Sorting of repos will and has already become increasingly important as more and more sources become available and used by a better performant pkg-mgm. * Basically the user just wants to group repos by their purpose and to sort repos by their importance as well as the resulting overall shape of their zypper repos display line. * Sorting in linear order by positional insertion(zypper) or mouse drags(yast) is straight forward and provides a feasible solution to manage to suffice all three sort-criteria. * It can be provided by the same command as rename-repo. That is orthogonal. No own command has to be remembered. The user, if not resource-empty, will have a try on this anyway (whether documented or not). * It is just a natural desire to reorder. We can reorder the pencils on the table, etc. It would be awkward if that was forbidden. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.