And yet those applications would still need to implement their own since they
operate on a different level (repo contents instead of local rpms). Supporting
multiple operations from the command like (ala #451 ) is the more rpm-like way
of doing it anyway.
--
You are receiving this because you
Closed #477.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/477#event-1789766543___
Rpm-maint mailing list
Rpm-maint@lists.rpm
If rpm supplied a simple REPL, exposed in the API, then there would be no need
to reimplement the same REPL stack (usually imperfectly) in multiple
applications, in multiple implementation languages.
--
You are receiving this because you are subscribed to this thread.
Reply to this email direct
IMO this should be done in high-level tools (like dnf) instead.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/477#issuecomment-412346708_
This RFE suggests creating a DSL (with commands like "install", "query", etc)
to process multiple commands from a single executable invocation.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-
