Hello Arun, thanks for your report!
What is not quite clear to me is that in the beginning, you say that people want to use the command line. Later you propose editing files, maybe in a simpler format than a programming language, but still files. Am Tue, Jun 30, 2026 at 12:00:18PM +0100 schrieb Arun Isaac: > This will enable us to write tooling like `guix manifest add pkg4`, etc. So this is where the command line comes in? Add a subcommand that edits these files? Then I am not even sure whether they need to be in a special format. You mention that arbitrary Scheme code is difficult to edit, but the simple example with a list of packages should be easy. Or let me formulate a thesis: Everything that is possible to do with a not very expressive declarative style, should be possible to do by automatically editing a Scheme file, maybe starting from a template (using "(substitute* ...", for instance). Are people's needs not already covered by the imperative style? guix package -i SOME_PACKAGE ? It is how I manage my "home profile", and it works very well for everyday work (if one is not worried about reproducibility, which is a step further that anyway requires more work). Andreas
