When opening Discover and going to Settings, there is a huge list of approximately 100 repos. If a newbie sees this, they tend to really hose their repos. Once this is done, it is a major problem to help them fix it, as they often cannot connect to any repos to do a sudo dnf reinstall distro-release-repos
and @ben79 , @rugyada and I have to walk them through a painful process to fix it all by hand. This is a frightening thing for the newbies. Any way around it is a good thing.
Discover reads every file in /etc/yum.repos.d and uses this to populate the list. This is a big problem. I do realize that all of the repo files need to be there, so that if a user changes their Update Channel, the needed repos are already there.
-
Is there a way to change the Backend, so that Discover does not see our repos? This would only allow Discover to see the KDE Store, Flathub and the Vendor repos for firmware. This is what Discover is good at. I don’t want to remove Discover.
-
is there a way to place a backup copy of /etc/yum.repos.d in /etc/skel/yum.repos.d and a script that we can have a user to run that would automatically restore these critical files without a connection to the repos?
Both of these things would be a big help. They do not have to be done at the same time. They can be separate projects.
Newbie Warning!
Never use this to modify your repos. It will break your system.