Description of problem: A newbie can be lost with a long list of repositories, for example when he want enable tainted repository. I suggest that the screen to enable/disable repositories can be of two levels, one standard and one advanced. I suggest that the repositories are displayed according two skill levels, for chosing which will be enabled. In the standard level, only the specific arch would be displayed, without debuginfo, nor source. In expert level, all repositories would be displayed. the display would be a table combined with tabs.
Created attachment 8970 [details] Suggested screens to display
CC: (none) => anaselli
i've thoutght to this a while... and i think that "normal user" should not enable/disable any "main" (core) repositories IMO. So that should be shown as enable/disable tainted and non-free only repos (and maybe additional ones) in Mageia and probably only copr ones in Fedora. "Expert users", e.g. expert view, should allow to see and modify all the repos instead. So the main aim should be understanding which are the main repos, and it should be great to have that from their meta-data.... WDYT?
I think that normal users would only manage main, nonfree, tainted, and copr repos. Beyond that is expert level. Maybe a simple switch if on x86_64 to enable/disable i586 counterparts for Mageia, since we have arched repos (rather than multiarch repos as Fedora does).
CC: (none) => ngompa13
@Neal, while normal user should disable main? IMO he/she could enable non free and tainted and maybe backports, since those are alternative repos with programs often wanted by looking here and there in the web...
why not while :)
Well, I think main should never be able to be disabled for the primary architecture :)
(In reply to Angelo Naselli from comment #2) > i've thoutght to this a while... and i think that "normal user" should not > enable/disable any "main" (core) repositories IMO. > So that should be shown as enable/disable tainted and non-free only repos > (and maybe additional ones) in Mageia and probably only copr ones in Fedora. > "Expert users", e.g. expert view, should allow to see and modify all the > repos instead. Hello, I think that main should be displayed to that it exists, even if disabling is not allowed. What about the local repositories on installation support? I don't see them. Can they be present or not? > So the main aim should be understanding which are the main repos, and it > should be great to have that from their meta-data.... I didn't find documentation about which data is available. GetRepo gives a Json string, but there is no indication on what is provided. A solution would be to provide a description file which gives templates of expected names for repositories.
(In reply to Neal Gompa from comment #3) > I think that normal users would only manage main, nonfree, tainted, and copr > repos. Beyond that is expert level. > Thus, do you mean that backports are of expert level? And that (Core and Core_updates), (nonfree and nonfree_updates) and (tainted and tainted_updates) are to enable/disable by couples? > Maybe a simple switch if on x86_64 to enable/disable i586 counterparts for > Mageia, since we have arched repos (rather than multiarch repos as Fedora > does). Yes, I like that idea
on comment #7 @papoteur the problem is always the widget we can manage :p I cannot disable a line, i can avoid that a line checked produces any changes, instead. From my point of view if we talk about "normal" users they most probably want to enable/disable backports, nonfree and tainted, so those one should be presented in a "normal" view, expoert one should show everything, even if not "checkable" in the meaning said above. But that needs an upstream step, i need to know if a repo is considered as -let's say- mandatory (e.g. main, update,... even with arch since they are privided by default from our distro - or fedora* for Fedora-) and that isn't available at the moment. In such a way mandatory repos, *-sources and *-debuginfo could be chosen to be displayed on expert view only. > What about the local repositories on installation support? I don't see them. > Can they be present or not? If you have installed them outside -dnfdragora can't atm- you can see them, in the case of the new implementation also because they are not -or better should not be- mandatory repos. >> So the main aim should be understanding which are the main repos, and it >> should be great to have that from their meta-data.... > I didn't find documentation about which data is available. GetRepo gives a > Json string, but there is no indication on what is provided. That Json is the only documentation i have, sorry. That's why i just show that atm, in further implementation we'll se what is important and present it better... (of course patches are always welcome :D)