Re: Announcing DNF 3 development

Matěj Cepl wrote: > When switching the programming langauge than I would think there > are some better C-successors than C++, namely Rust? Mad rush of > giving up on 46 years old language and switching to one which is > just 33 years old seems a bit bizarre to me. But the "33 years old" language

Re: Announcing DNF 3 development

On Mon, Mar 26, 2018 at 12:10 PM, Martin Kolman 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 wrote: >> > >> > >> > Dne 26.3.2018 v 10:16 Tom Hughes napsal(a): >> > > On 26/03/18 09:06,

Re: Announcing DNF 3 development

On Mon, Mar 26, 2018, at 11:02 AM, Vít Ondruch wrote: > 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. FWIW rpm-ostree is always a daemon

Re: Announcing DNF 3 development

On Mon, 2018-03-26 at 11:59 -0400, Neal Gompa wrote: > On Mon, Mar 26, 2018 at 11:02 AM, Vít Ondruch 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: > > >

Re: Announcing DNF 3 development

On Mon, Mar 26, 2018 at 11:02 AM, Vít Ondruch 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

Re: Announcing DNF 3 development

Le lundi 26 mars 2018 à 17:02 +0200, Vít Ondruch a écrit : > > 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. Yes that would be pretty awesome

Re: Announcing DNF 3 development

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

Re: Announcing DNF 3 development

On Mon, Mar 26, 2018 at 9:58 AM, Martin Sehnoutka wrote: > > > On 03/26/2018 02:30 PM, Neal Gompa wrote: >> On Mon, Mar 26, 2018 at 8:26 AM, Martin Sehnoutka >> wrote: >>> >>> >>> On 03/26/2018 01:38 PM, Neal Gompa wrote: On Mon, Mar 26, 2018 at

Re: Announcing DNF 3 development

On 03/26/2018 02:30 PM, Neal Gompa wrote: > On Mon, Mar 26, 2018 at 8:26 AM, Martin Sehnoutka wrote: >> >> >> On 03/26/2018 01:38 PM, Neal Gompa wrote: >>> On Mon, Mar 26, 2018 at 7:22 AM, Matěj Cepl wrote: On 2018-03-26, 10:52 GMT, Florian Weimer

Re: Announcing DNF 3 development

On Mon, Mar 26, 2018 at 8:26 AM, Martin Sehnoutka wrote: > > > On 03/26/2018 01:38 PM, Neal Gompa wrote: >> On Mon, Mar 26, 2018 at 7:22 AM, Matěj Cepl wrote: >>> On 2018-03-26, 10:52 GMT, Florian Weimer wrote: On 03/22/2018 01:40 PM, Daniel Mach wrote:

Re: Announcing DNF 3 development

On Mon, 2018-03-26 at 13:22 +0200, Matěj Cepl wrote: > On 2018-03-26, 10:52 GMT, Florian Weimer wrote: > > On 03/22/2018 01:40 PM, Daniel Mach wrote: > > > Please read more details on our blog: > > > https://rpm-software-management.github.io/announcement/2018/03/22/dnf-3-announcement/ > > > >

Re: Announcing DNF 3 development

On 03/26/2018 01:38 PM, Neal Gompa wrote: > On Mon, Mar 26, 2018 at 7:22 AM, Matěj Cepl wrote: >> On 2018-03-26, 10:52 GMT, Florian Weimer wrote: >>> On 03/22/2018 01:40 PM, Daniel Mach wrote: Please read more details on our blog:

Re: Announcing DNF 3 development

On Mon, Mar 26, 2018 at 7:22 AM, Matěj Cepl wrote: > On 2018-03-26, 10:52 GMT, Florian Weimer wrote: >> On 03/22/2018 01:40 PM, Daniel Mach wrote: >>> Please read more details on our blog: >>> https://rpm-software-management.github.io/announcement/2018/03/22/dnf-3-announcement/ >>

Re: Announcing DNF 3 development

On 2018-03-26, 10:52 GMT, Florian Weimer wrote: > On 03/22/2018 01:40 PM, Daniel Mach wrote: >> Please read more details on our blog: >> https://rpm-software-management.github.io/announcement/2018/03/22/dnf-3-announcement/ > > “C++ 11 is supported by GCC in RHEL 7 / CentOS 7” — You should > use

Re: Announcing DNF 3 development

On 03/22/2018 01:40 PM, Daniel Mach wrote: 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:

Re: Announcing DNF 3 development

On Mon, 2018-03-26 at 11:44 +0300, Jonathan Dieter wrote: > I've been working on zchunk which will allow downloading only the delta > of the metadata. For reference, the proposal starts at http://lists.rpm.org/pipermail/rp m-ecosystem/2018-February/000534.html. Jonathan

Re: Announcing DNF 3 development

> On 26. Mar 2018, at 10:39, Oron Peled wrote: > > On Monday, 26 March 2018 11:16:14 IDT Tom Hughes wrote: >> On 26/03/18 09:06, Marcin Juszkiewicz wrote: >>> Debian has APT. APT uses one copy of metadata. Be wise. Like Debian. >> >> Do we know how? Do they just not allow

Re: Announcing DNF 3 development

On Mon, 2018-03-26 at 09:30 +0100, Richard Hughes wrote: > With version 3.0 dnf is switching to the codebase we originally wrote > for PackageKit (libzif->libhif->libdnf), and so it inherits the > "download complete cache and switch atomically" logic. This means we > get a shared cache for free.

Re: Announcing DNF 3 development

On Monday, 26 March 2018 11:16:14 IDT Tom Hughes wrote: > On 26/03/18 09:06, Marcin Juszkiewicz wrote: > > Debian has APT. APT uses one copy of metadata. Be wise. Like Debian. > > Do we know how? Do they just not allow non-root users to get up > to date data, or do they do something cleverer?

Re: Announcing DNF 3 development

On 26/03/18 09:30, Richard Hughes wrote: On 26 March 2018 at 09:16, Tom Hughes wrote: 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? I think he means removing the duplication of the

Re: Announcing DNF 3 development

W dniu 26.03.2018 o 10:16, Tom Hughes pisze: > On 26/03/18 09:06, Marcin Juszkiewicz wrote: >> 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? Use. Not download. And inform (like always) how old that

Re: Announcing DNF 3 development

On 26 March 2018 at 09:16, Tom Hughes wrote: >> 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? I think he means removing the duplication of the cache between PackageKit and dnf. The

Re: Announcing DNF 3 development

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

Re: Announcing DNF 3 development

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: >

Re: Announcing DNF 3 development

On Fri, 2018-03-23 at 10:55 -0500, Ian Pilcher wrote: > On 03/22/2018 07:40 AM, Daniel Mach wrote: > > 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. > >

Re: Announcing DNF 3 development

On 03/22/2018 07:40 AM, Daniel Mach wrote: 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:

Re: Announcing DNF 3 development

On Thu, Mar 22, 2018, 23:13 Nico Kadel-Garcia wrote: > On Thu, Mar 22, 2018 at 5:49 PM, John Reiser wrote: > > On 03/22/2018 01:51 PM, Nico Kadel-Garcia wrote: > >> > >> On Thu, Mar 22, 2018 at 10:52 AM, John Reiser > >> wrote: >

Re: Announcing DNF 3 development

On Thu, Mar 22, 2018 at 5:49 PM, John Reiser wrote: > On 03/22/2018 01:51 PM, Nico Kadel-Garcia wrote: >> >> On Thu, Mar 22, 2018 at 10:52 AM, John Reiser >> wrote: >>> >>> On 03/22/2018 05:40 AM, Daniel Mach wrote: We are pleased to

Re: Announcing DNF 3 development

On 22 March 2018 at 17:49, John Reiser wrote: > On 03/22/2018 01:51 PM, Nico Kadel-Garcia wrote: >> >> On Thu, Mar 22, 2018 at 10:52 AM, John Reiser >> wrote: >>> >>> On 03/22/2018 05:40 AM, Daniel Mach wrote: We are pleased to announce

Re: Announcing DNF 3 development

On 03/22/2018 01:51 PM, Nico Kadel-Garcia wrote: On Thu, Mar 22, 2018 at 10:52 AM, John Reiser wrote: On 03/22/2018 05:40 AM, Daniel Mach wrote: We are pleased to announce that development of DNF 3 has started. This version is focused on performance improvements, new

Re: Announcing DNF 3 development

On Thu, Mar 22, 2018 at 10:52 AM, John Reiser wrote: > On 03/22/2018 05:40 AM, Daniel Mach wrote: >> >> 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

Re: Announcing DNF 3 development

On 03/22/2018 05:40 AM, Daniel Mach wrote: 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. How does RPM fit into DNF's view of "the whole software management

Re: [Rpm-ecosystem] Announcing DNF 3 development

On Thu, Mar 22, 2018 at 8:40 AM, Daniel Mach wrote: > 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

Announcing DNF 3 development

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: