From: Amirouche Boubekki <amirouche@hypermove.net>
To: David Thompson <dthompson2@worcester.edu>
Cc: 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 10:56:40 +0200 [thread overview]
Message-ID: <1baf47b773872ca3663600b2fdb3888e@hypermove.net> (raw)
In-Reply-To: <57add006a9e098fd69e269f1082262c7@hypermove.net>
Le 2015-08-19 10:27, Amirouche Boubekki a écrit :
> 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.
>
> On a similar note, I like a lot the idea of Andy Wingo `guix install`
> and `guix search`.
To be precise I prefer, `guix package install` and `guix package search`
(which is not the subject of patch of Andy Wingo).
next prev parent reply other threads:[~2015-08-19 8:56 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 [this message]
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
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=1baf47b773872ca3663600b2fdb3888e@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).