unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Amirouche Boubekki <amirouche@hypermove.net>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>,
	guix-devel-bounces+amirouche=hypermove.net@gnu.org
Subject: Re: [PATCH] scripts: package: Add --install-from-file option.
Date: Wed, 19 Aug 2015 17:31:55 +0200	[thread overview]
Message-ID: <60d219d4d56e5edce70da79239efc059@hypermove.net> (raw)
In-Reply-To: <CAJ=RwfaRCSOXypqesxUBXO63pYsOffNboV-b7quXD1TCHMKy7w@mail.gmail.com>

Le 2015-08-19 15:04, Thompson, David a écrit :
> On Wed, Aug 19, 2015 at 4:27 AM, Amirouche Boubekki
> <amirouche@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.

Thanks.

> How can one tell if a package spec or a file name was passed
> with 100% accuracy?

Honestly I have the feeling that you are pushing your idea more than 
trying to make things better.

- Adding the `-f` modifier won't help make guix package command easy to 
the mind.

- Especially since the command it will replace is simple

- The command targets developpers and is only useful in the context of 
building project from sources which are not released. It can go inside a 
Makefile.

For this reason I don't like it being inside guix.

> You can't, and we'd have to use a heuristic that
> would surely fail in some awful way for someone.  It's best for this
> to be a separate argument.

You know you are wrong. You can simply ban packages which ends with .scm 
which is not too difficult to do and is already possible with current 
packages.

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 get lost and don't remember all the apt-foo commands and what they are 
supposed to do. Using this scheme will keep each subcommand --help (or 
just help) more readable.

  parent reply	other threads:[~2015-08-19 15:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 15:59 [PATCH] scripts: package: Add --install-from-file option David Thompson
2015-08-10 14:22 ` Alex Kost
2015-08-18 19:30 ` Ludovic Courtès
2015-08-19  0:17   ` Thompson, David
2015-08-19 22:38     ` Ludovic Courtès
2015-08-20  2:26       ` Thompson, David
2015-08-19  8:27 ` Amirouche Boubekki
2015-08-19  8:56   ` Amirouche Boubekki
2015-08-19 14:48     ` Claes Wallin (韋嘉誠)
2015-08-19 13:04   ` Thompson, David
2015-08-19 13:54     ` Taylan Ulrich Bayırlı/Kammer
2015-08-19 15:31     ` Amirouche Boubekki [this message]
2015-08-19 19:15       ` Alex Kost

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60d219d4d56e5edce70da79239efc059@hypermove.net \
    --to=amirouche@hypermove.net \
    --cc=dthompson2@worcester.edu \
    --cc=guix-devel-bounces+amirouche=hypermove.net@gnu.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).