dnf-0.4.11

[Alec Leamas]

First of all, this is not, and have never been a question of disabled
repos. Or should not have. "yum clean all" refers to cleaning all metadata,
not all repos. It only operates on one single repo, be it implicit (the
default link) or an explicit -r option.

This is what confuses. I know:  been there done that... Even though the
documents are clear, the behaviour does indeed cause confusion for some
reason even though it's well-defined.

Of course, changing semantics for yum is a bad idea, agreed. I did not have
anything like that in mind. At most, some info on what buildroot which is
used in the output, or similar measures.

For dnf, I guess one could possibly think somewhat more free. Personally, I
tend to think that it's the implicit buildroot which causes much of this
trouble.

What happens if we get rid of the implcit buildroot, forcing us to specify
it every time? With 'default' as a legal option? Personally, I tend to
think this might make things a little clearer.

Just my 5 öre
--alec


On Mon, Jan 13, 2014 at 12:17 AM, Orcan Ogetbil <oget.fedora at gmail.com>wrote:

> On Sun, Jan 12, 2014 at 5:23 PM, Alec Leamas wrote:
> > Well, IMHO the docs are actually quite clear on that 'all' refers to all
> > metadata rather than all repositories.
> >
> > That said, perhaps enough people has been confused by this to make some
> kind
> > of improvement motivated.
> >
>
> I am pretty sure if you flip the current behavior and make 'clean all'
> act on disabled repos, some other subset of users (e.g. me) will be
> confused.
>
> Best,
> Orcan
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20140113/afe0304a/attachment-0001.html>