Re: [Rpm-ecosystem] DNF team would like to take over libdnf ownership

2017-12-01 Thread Colin Walters
On Mon, Oct 30, 2017, at 05:48 AM, Daniel Mach wrote: > We are getting requests to implement more features in microdnf, > such as modularity[1][2], unify repo cache and overall business logic. > Porting big portions of existing DNF code (Python) into a C library > seems to be the only feasible

Re: [Rpm-ecosystem] DNF team would like to take over libdnf ownership

2017-10-30 Thread Neal Gompa
On Mon, Oct 30, 2017 at 3:15 PM, Daniel Mach wrote: > > > On Mon, Oct 30, 2017 at 12:43 PM, Neal Gompa wrote: >> >> On Mon, Oct 30, 2017 at 6:48 AM, Daniel Mach wrote: >> > Hi everyone, >> > My name is Daniel Mach and I'm leading the DNF

Re: [Rpm-ecosystem] DNF team would like to take over libdnf ownership

2017-10-30 Thread Neal Gompa
On Mon, Oct 30, 2017 at 3:32 PM, Daniel Mach wrote: > > > On Mon, Oct 30, 2017 at 2:02 PM, Colin Walters wrote: >> >> On Mon, Oct 30, 2017, at 07:43 AM, Neal Gompa wrote: >> > * Using C++ makes glib2 usage mostly pointless, as glib2 is by and >> > large

Re: [Rpm-ecosystem] DNF team would like to take over libdnf ownership

2017-10-30 Thread Daniel Mach
On Mon, Oct 30, 2017 at 2:21 PM, Colin Walters wrote: > > (Actually, *are* we keeping DNF in Python?) > Yes for now. Not sure if we can drop it in the future, as we may need to support python plugins. Anyway, this is definitely not an immediate priority...

Re: [Rpm-ecosystem] DNF team would like to take over libdnf ownership

2017-10-30 Thread Daniel Mach
On Mon, Oct 30, 2017 at 2:02 PM, Colin Walters wrote: > On Mon, Oct 30, 2017, at 07:43 AM, Neal Gompa wrote: > > * Using C++ makes glib2 usage mostly pointless, as glib2 is by and > > large replaced by the C++ STL. The only advantage of GLib2 is GObject > > Introspection > >

Re: [Rpm-ecosystem] DNF team would like to take over libdnf ownership

2017-10-30 Thread Daniel Mach
On Mon, Oct 30, 2017 at 12:43 PM, Neal Gompa wrote: > On Mon, Oct 30, 2017 at 6:48 AM, Daniel Mach wrote: > > Hi everyone, > > My name is Daniel Mach and I'm leading the DNF team. > > > > > > TL;DR: > > > > The DNF team wants to take libdnf over and

Re: [Rpm-ecosystem] DNF team would like to take over libdnf ownership

2017-10-30 Thread Colin Walters
On Mon, Oct 30, 2017, at 09:15 AM, Neal Gompa wrote: > As much as I like Rust, it's hampered more by LLVM than anything else. > I struggle to see the advantage of writing in Rust. Not to mention > that the learning curve is quite high compared to other languages. I'd > be more likely to suggest

Re: [Rpm-ecosystem] DNF team would like to take over libdnf ownership

2017-10-30 Thread Colin Walters
On Mon, Oct 30, 2017, at 07:43 AM, Neal Gompa wrote: > * Using C++ makes glib2 usage mostly pointless, as glib2 is by and > large replaced by the C++ STL. The only advantage of GLib2 is GObject > Introspection Not quite; there's also the main event loop, which is also tied into infrastructure

Re: [Rpm-ecosystem] DNF team would like to take over libdnf ownership

2017-10-30 Thread Neal Gompa
On Mon, Oct 30, 2017 at 6:48 AM, Daniel Mach wrote: > Hi everyone, > My name is Daniel Mach and I'm leading the DNF team. > > > TL;DR: > > The DNF team wants to take libdnf over and re-start development, which would > possibly include using C++ (only to limited and reasonable

Re: [Rpm-ecosystem] DNF team would like to take over libdnf ownership

2017-10-30 Thread Igor Gnatenko
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2017-10-30 at 11:48 +0100, Daniel Mach wrote: > Hi everyone, > My name is Daniel Mach and I'm leading the DNF team. > > > TL;DR: > > The DNF team wants to take libdnf over and re-start development, > which would > possibly include using