On Wed, Mar 13, 2019 at 1:42 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote:
>
> On Wed, Mar 13, 2019 at 8:39 AM Miroslav Suchý <msuchy@xxxxxxxxxx> wrote:
> >
> > Hi,
> > I am curious whether we can move our repo files from
> > /etc/yum.repos.d
> > to
> > /etc/distro.repos.d
Why not /etc/dnf/repos.d and a symlink for /etc/yum.repos.d?
> > In Fedora 31 we are going to wipe away last left overs of YUM, so it really does not have sense to keep `yum.repos.d`.
> >
> > DNF for ages parse config files from:
> > {"/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d"}
> > Therefore the move of repo files does not require any change in DNF. It should be just change in fedora-repos.
> > If anyone put his private repos to /etc/yum.repos.d then DNF will parse it too. From DNF point of view, the files can be
> > split randomly across all those directories.
> >
> > Of course, that directory is mentioned everywhere in documentation and it will take ages to change it as it is written
> > everywhere. But the other option is to stuck with yum.repos.d forever.
> >
> > Is there anything which can block this move?
> >
>
> Nothing except bikeshedding. :)
>
> That said, I think if we want to move the repo files now, we should
> also consider making so package installed repo and GPG files are in
> /usr/share and that admin additions/overrides can be stored in /etc.
> Same goes for vars and other such stuff.
Agreed, but it would be nice to have tooling to list repos, see their
origin and whether or not they were overridden.
> That's more or less the mechanism we've adopted for tons of other
> things, and it'd be nice to have it in DNF too...
Wasn't systemd the catalyst for this?
Dridi
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
