On Mon, 2 Nov 2020 at 21:38, Daniel Mach <dm...@redhat.com> wrote:
>
> Lazy file list loading? Yes, that's on DNF's TODO list already, but (to
> be honest) not on top - there's always something more important. It's
> not getting into DNF4, but it may get into DNF5 later on.

Ok, good to know.

Best regards
clime
>
>
> Dne 02. 11. 20 v 20:13 clime napsal(a):
> > On Mon, 2 Nov 2020 at 18:55, Vít Ondruch <vondr...@redhat.com> wrote:
> >>
> >>
> >> Dne 01. 11. 20 v 11:58 clime napsal(a):
> >>> Hello!
> >>>
> >>> First of all, I don't really know what I am talking about here but I
> >>> noticed the `dnf update` operation downloads among other things
> >>> `filelists.xml` (optionally compressed by zchunk, thanks Jonathan
> >>> Dieter!!!) and I remember there was a thread on devel mailing quite
> >>> some time ago by Zbyszek from which I understood this data is only
> >>> needed when filesystem paths are used as package requirements or when
> >>> a fs path is specified as direct argument to `dnf install`.
> >>
> >>
> >> This was the case for Yum, but have never the case for DNF since its
> >> beginning. I think there were some reasons, such as that the solver in
> >> case it finds it needs them would need to stop, download the data and
> >> start from beginning. Other reason could be that nobody optimized it yet.
> >>
> >> Anyway, I guess you'll find more info in Bugzilla.
> >
> > Hello vit, thank you very much, I will try to look it up. M.
> >
> >>
> >>
> >> V.
> >>
> >>
> >>>    Could we
> >>> then, please, trigger download of this file only if and when needed
> >>> and not sooner? It seems to take more than half of the total download
> >>> size e.g. for fedora-32-updates repo so it could improve repodata
> >>> download times quite significantly. Again, I don't really know what I
> >>> am talking about here but this came to my mind recently so I wanted to
> >>> write it down just in case it would be possible :).
> >>>
> >>> Thank you very much
> >>> clime
> >>> _______________________________________________
> >>> devel mailing list -- devel@lists.fedoraproject.org
> >>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> >>> Fedora Code of Conduct: 
> >>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >>> List Archives: 
> >>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> >> _______________________________________________
> >> devel mailing list -- devel@lists.fedoraproject.org
> >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> >> Fedora Code of Conduct: 
> >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives: 
> >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> > _______________________________________________
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> >
>
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to