On Thu, Apr 21, 2022 at 10:01 AM Colin Walters wrote:
>
>
>
> On Thu, Apr 21, 2022, at 7:19 AM, Zbigniew Jędrzejewski-Szmek wrote:
> >
> > - dnf-daemon would be dbus-activated and exit-on-idle after a suitable
> > timeout
>
> This is how rpm-ostree has worked for about 5 years now:
>
On Thu, Apr 21, 2022, at 7:19 AM, Zbigniew Jędrzejewski-Szmek wrote:
>
> - dnf-daemon would be dbus-activated and exit-on-idle after a suitable
> timeout
This is how rpm-ostree has worked for about 5 years now:
https://github.com/coreos/rpm-ostree/pull/606
(Lots of useful references in that
On Thu, Apr 21, 2022 at 6:56 AM Miroslav Suchý wrote:
>
> Dne 20. 04. 22 v 8:55 Jaroslav Mracek napsal(a):
>>
>>
>> I've gotta ask... How much memory does the new dnf daemon take while idle?
>
>
> We do not have any measurements right now. Please feel free to test it. We
> have a repository with
On Thu, Apr 21, 2022 at 12:45:48PM +0200, Miroslav Suchý wrote:
> Dne 20. 04. 22 v 8:55 Jaroslav Mracek napsal(a):
> >
> >
> > I've gotta ask... How much memory does the new dnf daemon take while
> > idle?
> After installation:
> Memory: 1.6M
> CPU: 23ms
>
> After upgrade of
Dne 20. 04. 22 v 8:55 Jaroslav Mracek napsal(a):
I've gotta ask... How much memory does the new dnf daemon take while idle?
We do not have any measurements right now. Please feel free to test it. We have a repository with DNF5/Microdnf
nightly builds -
On Thu, Apr 21, 2022 at 11:01 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> > * Compatibility
> > ** To improve user experience and to unify dnf/microdnf behavior we
> > were unable to keep 100% compatibility with formal Microdnf in
> > command-line and in behavior
>
> Can you comment more on this
> * Compatibility
> ** To improve user experience and to unify dnf/microdnf behavior we
> were unable to keep 100% compatibility with formal Microdnf in
> command-line and in behavior
Can you comment more on this part? yum/dnf command-line and behaviour
compatiblity made adoption fairly easy. (I
> https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf
Overall, the new architecture is a huge improvement and should fix many
of the long-standing issues.
Would it be possible to extend the How To Test section with installation
and commandline-use instructions? Is the stuff planned in
On 4/13/22 23:28, Gordon Messmer wrote:
I've gotta ask... How much memory does the new dnf daemon take while idle?
I know this comes up time to time... As it is, PackageKitd and gnome-software
both, individually, take ~ 450MB of RAM without any user interaction (other
than logging in to a
On Thu, Apr 14, 2022 at 8:48 PM Chris Snyder wrote:
> For dnf plugin writers, what will the migration path look like to switch
> over to be compatible with microdnf?
>
The new Plugins for LIBDNF5 or Microdnf will be required to use the new API
therefore it will be required to rewrite them. The
On Thu, Apr 14, 2022 at 8:30 AM Gordon Messmer
wrote:
> On 4/12/22 13:54, Ben Cotton wrote:
> > == Detailed Description ==
> > The new major Microdnf will provide huge improvements and in some
> > cases better behavior then DNF. In the future, the new Microdnf will
> > replace DNF. The new
For dnf plugin writers, what will the migration path look like to switch
over to be compatible with microdnf?
On Thu, Apr 14, 2022 at 8:05 AM Neal Gompa wrote:
> On Thu, Apr 14, 2022 at 7:40 AM Kevin Kofler via devel
> wrote:
> >
> > Gordon Messmer wrote:
> > > I've gotta ask... How much
On Thu, Apr 14, 2022 at 7:40 AM Kevin Kofler via devel
wrote:
>
> Gordon Messmer wrote:
> > I've gotta ask... How much memory does the new dnf daemon take while idle?
>
> As I understand it, the new DNF daemon would mostly only replace/upgrade the
> already existing dnfdaemon, for users of tools
Gordon Messmer wrote:
> I've gotta ask... How much memory does the new dnf daemon take while idle?
As I understand it, the new DNF daemon would mostly only replace/upgrade the
already existing dnfdaemon, for users of tools like Dnfdragora. It would not
be required otherwise, or would it?
On Wed, Apr 13, 2022 at 4:30 PM Kevin Kofler via devel <
devel@lists.fedoraproject.org> wrote:
> Neal Gompa wrote:
> > dnf, microdnf
>
> Doesn't the change page say the Python DNF will go away?
>
This question will be addressed in a separate change proposal. Fedora 39
can be taken as a primary
On 4/12/22 13:54, Ben Cotton wrote:
== Detailed Description ==
The new major Microdnf will provide huge improvements and in some
cases better behavior then DNF. In the future, the new Microdnf will
replace DNF. The new Microdnf will be accompanied by a new library
(`libdnf5`) and a new DNF
On 4/12/22 16:54, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf
>
> == Summary ==
> A major upgrade of Microdnf is the first step in the evolution of
> package management in Fedora. The new microdnf has ambitions to
> provide all major features of DNF without
Neal Gompa wrote:
> dnf, microdnf
Doesn't the change page say the Python DNF will go away?
I would welcome a pure C/C++ base system, with no language interpreters
beyond bash.
Kevin Kofler
___
devel mailing list --
On Wed, Apr 13, 2022 at 10:07 AM Mattia Verga via devel
wrote:
>
> Il 12/04/22 22:54, Ben Cotton ha scritto:
> > https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf
> >
> > == Summary ==
> > A major upgrade of Microdnf is the first step in the evolution of
> > package management in
Il 12/04/22 22:54, Ben Cotton ha scritto:
> https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf
>
> == Summary ==
> A major upgrade of Microdnf is the first step in the evolution of
> package management in Fedora. The new microdnf has ambitions to
> provide all major features of DNF
On Wed, Apr 13, 2022 at 10:15 AM Vít Ondruch wrote:
>
> Dne 12. 04. 22 v 22:54 Ben Cotton napsal(a):
> > https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf
> >
> > == Summary ==
> > A major upgrade of Microdnf is the first step in the evolution of
> > package management in Fedora. The
Dne 12. 04. 22 v 22:54 Ben Cotton napsal(a):
https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf
== Summary ==
A major upgrade of Microdnf is the first step in the evolution of
package management in Fedora. The new microdnf has ambitions to
provide all major features of DNF without
https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf
== Summary ==
A major upgrade of Microdnf is the first step in the evolution of
package management in Fedora. The new microdnf has ambitions to
provide all major features of DNF without losing its minimal
footprint.
== Owner ==
*
https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf
== Summary ==
A major upgrade of Microdnf is the first step in the evolution of
package management in Fedora. The new microdnf has ambitions to
provide all major features of DNF without losing its minimal
footprint.
== Owner ==
*
24 matches
Mail list logo
