On 14. 6. 2014 at 12:18:07, Jon Kent wrote: > Hi, > > Been monitoring this debate and if nothing else this seems to point out > that the reasoning for dnf, as opposed to fixing/rewriting yum haven't been > laid out very well. I'm on yum side of the fence as I don't see that the > reasoning so far is been put forward very well for moving to dnf, and that > dnf has crept up on people rather than being 'out there'. > > Played with dnf, and from as SA point of view (i.e. mine), I don't see the > difference really, does what I need, which is good. But then so does yum, > and there lies the problem. Bad/undocumented api's is not a good reason > for starting something from starch, but a good reason to write this. At > present, this feels like a pet project, rather than a project with good > reasoning for existing. I'm sure that not the case, but its not good that > I, and others, feel this well and points to really bad communication. > > So my message is simple, write up why dnf is better than yum, from both a > users and devs point of view, then maybe this'll win people over. Till I > see that, I'll back the guys who want to stick with yum. Hi Jon, I will make this as short and simple as possible: - dnf is maintainable in long term perspective, yum is not - dnf's well defined architecture allows: -- RFEs to come in more easily -- other programs to integrate better with it The transition has nothing to do with user experience, it's all about the people making it. If someone steps up who is willing to maintain yum and keep up with the development in the area of rpm-based software management, be my guest. To give you an example of what I'm talking about: recently we have introduced a concept of soft dependencies in rpm (yes, those that you know from Debian). Dnf will be able to handle them almost out of the box. Yum will maybe support them with some effort. Then we have the next big thing coming: rich dependencies (basically a simple boolean algebra in deps). There is no plan for yum to support those, the amount of effort required will just not be worth it. Thanks Jan -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
