dmnks left a comment (rpm-software-management/rpm#3653)
One advantage of this "plugin" architecture would be that we'd get the
old-style executables "for free", by simply leaving `rpmbuild`, `rpmsign`,
`rpmkeys` etc. alone and just dispatching to them from that central `rpm`
wrapper. It would also allow for keeping popt out of the picture here.
The easy extensibility (of adding new subcommands) would be a nice side effect,
although I agree it's not necessarily something we'd want to endorse. It could
lead to proliferation of rpm-related tooling on your system that doesn't really
belong to the `rpm` command namespace after all. There's no deeper integration
support in that model either, it just allows you to replace a command like
`rpm-foo` with `rpm foo` which is just a cosmetic improvement.
Something I also realize now is that it wouldn't "scale" very well in terms of
adding sub-sub-commands, which we might want to do at some point, e.g. `rpm
keys add`, etc.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3653#issuecomment-2880169451
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3653/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
https://lists.rpm.org/mailman/listinfo/rpm-maint
