On Mon, Mar 26, 2018 at 12:10 PM, Martin Kolman <mkolman@xxxxxxxxxx> wrote: > On Mon, 2018-03-26 at 11:59 -0400, Neal Gompa wrote: >> On Mon, Mar 26, 2018 at 11:02 AM, Vít Ondruch <vondruch@xxxxxxxxxx> wrote: >> > >> > >> > Dne 26.3.2018 v 10:16 Tom Hughes napsal(a): >> > > On 26/03/18 09:06, Marcin Juszkiewicz wrote: >> > > > W dniu 22.03.2018 o 13:40, Daniel Mach pisze: >> > > > > We are pleased to announce that development of DNF 3 has started. This >> > > > > version is focused on performance improvements, new API and >> > > > > consolidating >> > > > > the whole software management stack. >> > > > > >> > > > > Please read more details on our blog: >> > > > > https://rpm-software-management.github.io/announcement/2018/03/22/dnf-3-announcement/ >> > > > > >> > > > >> > > > Will it FINALLY use one copy of metadata for all system users? >> > > >> > > Do you have a proposal as to how that might be possible in a >> > > secure way? >> > >> > If DNF was just frontend for some service/daemon, that would be one >> > possibility. It would also help with other issues like updates of X >> > server crashing whole user session and therefore the update. >> > >> >> It would be nice if dnfdaemon was actually merged into dnf itself, but >> I'm not sure whether they'd consider it to be desirable or not. > I have a hunch there will be some gotchas, otherwise everybody would be doing it. > > Maybe issues with chrooting or something like that ? We'd probably want a no-daemon switch for changing behavior, and trigger that change for circumstances where the daemon cannot run. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
