Re: F25 System Wide Change: Use /etc/distro.repos.d as default reposdir

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> From: "Ted W." <ted-lists@xxxxxxx>
> 
> I'll jump on the /etc/repos.d bandwagon. It follows a convention
> commonly found in lots of other configuration directories and I feel
> it's much more concise and clear than /etc/distro.repos.d.
> 
> I'm not sure I fully understand the rationale behind using
> distros.repos.d as the directory name in the first place. Distros, in
> the Linux context, suggest something fairly well defined; variants of
> the Linux based operating systems. To stick with the the original
> justification:
> 
>  > [...] /etc/distro.repos.d path is a
> package manager agnostic name [...]
> 
> I would think something called /etc/software.repos.d or
> /etc/vendors.repos.d would make more sense if you really want to keep
> the foo.bar.d convention.
> 
> On 05/16/2016 04:59 AM, Miroslav Suchý wrote:
> > Dne 12.5.2016 v 17:51 Mike Chambers napsal(a):
> >> Hell, if really want to make it simple, why not just /etc/repos.d?
> >
> > +1

Hi,

there are a lot of good suggestions about the path name in the discussion.
`/etc/distro.repos.d` probably wasn't the best chosen path so we've changed
it to `/etc/repos.d` in the proposal. Moreover I've mentioned there possible path name
alternatives like /etc/software.repos.d, /etc/vendors.repos.d, /etc/rpm.repos.d,
/etc/rpm-md.repos.d, /etc/system.repos.d. The type of the metadata format could
be defined by `type` option in the file itself like Suse does so we don't need
to have any specifier before `repos.d`.


> From: "Dennis Gilmore" <dennis@xxxxxxxx>
> 
> As others have mentioned I do not think that distro.repos.d is not really
> appropriate. I also suspect that the idea of putting them in /usr/lib/
> somewhere and allowing local overriding py dropping snippets in /etc/ will be
> a lot fo work to yum adding new features that we probably do not want to do.
> 
> rpm.repos.d may be the best name if we grow to support maven, npm, rubygems,
> etc repos  they could use <packagemanager>.repos.d for consistency

`/etc/rpm.repos.d` - indicate it's a directory with configuration files to
rpm package so `/etc/rpm-md.repos.d` would be IMO preferable.


> From: "Remi Collet" <Fedora@xxxxxxxxxxxxxxxxx>
> To: devel@xxxxxxxxxxxxxxxxxxxxxxx
> Sent: Friday, May 13, 2016 1:00:09 PM
> Subject: Re: F25 System Wide Change: Use /etc/distro.repos.d as default reposdir
> 
> Le 12/05/2016 à 09:36, Jan Kurik a écrit :
> > = Proposed System Wide Change: Use /etc/distro.repos.d as default reposdir
> > =
> > https://fedoraproject.org/wiki/Changes/ReposInEtcDistroReposD
> 
> 
> Perhaps the 1st goal should be
> "have compatible configuration files for yum and dnf".
> 
> For memory this is not true
> 
> - "includepkgs" for yum doesn't work with dnf
> - "include" for dnf breaks yum.

This will be compatible with yum again in DNF-2.0. Some of the yum options,
PK and DNF does not currently understand though.


Honza
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux