Amirouche Boubekki (2015-08-19 18:31 +0300) wrote: > Le 2015-08-19 15:04, Thompson, David a écrit : >> On Wed, Aug 19, 2015 at 4:27 AM, Amirouche Boubekki >> <amirou...@hypermove.net> wrote: >>> Le 2015-08-09 17:59, David Thompson a écrit : >>>> >>>> In my personal projects, I keep a 'package.scm' file in the root of >>>> the >>>> source tree for use with 'guix environment -l'. However, it's also >>>> handy to install that package by using 'guix package -e': >>>> >>>> guix package -e '(primitive-load "package.scm")' >>>> >>>> This patch adds a shorthand for this: >>>> >>>> guix package -f package.scm >>> >>> >>> What about dispatch `guix package -i` depending on the argument. In >>> principle there will be no "*.scm$" packages so the above could be >>> >>> guix package -i package.scm >>> >>> The idea behind that is to keep the number of command to minimum. In >>> this >>> case, IMO, it makes sens to merge both logic inside the same UI. >> >> That won't work because it creates ambiguities in the package spec >> syntax.
I agree with David on another option instead of adding a special case to "--install". I think you can't rely on ".scm" extension. [...] > My opinion, is that instead of adding options/modifiers to "guix > package", it should be split into "guix package install", "guix package > search", "guix package show" and "guix package generation". It might not > be obvious and is afaik not a cli layout that is widespread but it will > greatly help people get their hands on guix. I would also like subcommands for "guix package" but what about simultaneous installing+removing that can be currently done with "guix package -i foo -r bar"? -- Alex