Re: [Rpm-ecosystem] rpm-ostree's usage of libhif/hawkey merge

2016-01-28 Thread Honza Šilhan
> From: "Neal Gompa" > Honestly, at this point, I'm wondering why we don't just rename libhif > to libdnf (or something else, but DNF would be the primary consumer). > Now that the hawkey/hif merger is (mostly) complete and it's one > library that was ultimately designed to be

Re: [Rpm-ecosystem] rpm-ostree's usage of libhif/hawkey merge

2016-01-26 Thread Colin Walters
On Tue, Jan 26, 2016, at 11:27 AM, Neal Gompa wrote: > That would break way too many things. What would break, exactly? > The problem with what your > suggesting that it implies you are the only consumer of libhif. I guess I didn't spell out that I was also suggesting we still support

Re: [Rpm-ecosystem] rpm-ostree's usage of libhif/hawkey merge

2016-01-26 Thread Colin Walters
On Tue, Jan 26, 2016, at 12:54 PM, Neal Gompa wrote: > Well, if you keep altering all the interfaces, especially the public > ones used by PackageKit and DNF, then there will be problems for > developers and consumers of these programs. What I'm trying to say is that given we know we need to

Re: [Rpm-ecosystem] rpm-ostree's usage of libhif/hawkey merge

2016-01-26 Thread Neal Gompa
On Tue, Jan 26, 2016 at 1:12 PM, Colin Walters wrote: > > > On Tue, Jan 26, 2016, at 12:54 PM, Neal Gompa wrote: > >> Well, if you keep altering all the interfaces, especially the public >> ones used by PackageKit and DNF, then there will be problems for >> developers and