On Thu, 2020-03-05 at 18:38 +0000, J. Randall Owens wrote:
On 04/03/2020 18:03, Daniel Mach wrote:
> Hello everyone,
> I'm pleased to announce start of DNF 5 development. We are planning to
> deliver a module stream or a COPR repo during Fedora 33 development for
> early adopters and tool developers and we're hoping in getting a stable
> version into Fedora 34.
> More details follow.
> We've managed to drop a lot of redundant code across the whole DNF stack
> in the past years, but we have reached a point when it's nearly
> impossible to consolidate the code any further without breaking the
> API/ABI. Especially with PackageKit being dead, we can't move with
> the old "libhif" API in libdnf, because making any bigger changes to
> PackageKit is clearly out of scope.
> That's why we decided to start working on a new version of the DNF
> stack: DNF 5. And this is the plan:
> 1. Consistency, documentation and user experience is the top priority.
> 2. Compatibility on the command line level.
> 3. Compatibility on the API level.
In favour of 1., but going against 2., I've wanted since the YUM days to
see more consistency in the compound-word* options. E.g., --enablerepo
but --skip-broken, and I have a hard time remembering which ones get the
hyphen inbetween*, and which ones don't. Could we settle on one way or
the other, right now quite the majority are without hyphen, and
deprecate the other (but presumably enable both spellings for a good
long while, perhaps with a warning if someone spells it the old way)?
Probably not take away the old spellings as soon as DNF 5, but it might
be a good time to add the more consistent spellings.
I mean, it shouldn't be too hard to standardize on having them all work
both ways, even.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net