all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: Tobias Geerinckx-Rice <somebody@not-sent-or-endorsed-by.tobias.gr>
Cc: 33647@debbugs.gnu.org
Subject: bug#33647: First `guix pull' behaves unexpectedly
Date: Thu, 20 Dec 2018 06:24:11 +0100	[thread overview]
Message-ID: <754f62aa-dd54-4b0e-b78e-052160295af2@riseup.net> (raw)
In-Reply-To: <87woo58ggz.fsf@nckx>

On 2018-12-19 20:27, Tobias Geerinckx-Rice wrote:
> swedebugia wrote:
>> egil@parabola:~$ time hash pacman
>>
>> real    0m0,000s
>> user    0m0,000s
>> sys    0m0,000s
>>
>> So it won't and any measuable overhead to just call this in the end of
>> guix package after updating the symlinks to the new profile
>> generation.
> 
> Do you mean to put something like
> 
>   guix() {
>     command "$1" "$@"
>     hash "$1"
>   }
> 
> in the default /etc/profile (or wherever such things belong)?
> 
> I think this is far too intrusive and magical to do by default, 
> considering its limited one-time-only usefulness.  The same goes for 
> patching shells.

That sounds like it could work even though it look like an ugly hack. :)

-- 
Cheers Swedebugia

  reply	other threads:[~2018-12-20  5:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 14:56 bug#33647: First `guix pull' behaves unexpectedly Diego Nicola Barbato
2018-12-06 15:42 ` Ricardo Wurmus
2018-12-06 17:03   ` Diego Nicola Barbato
2018-12-06 23:06   ` Ludovic Courtès
2018-12-07  8:36     ` Diego Nicola Barbato
2018-12-07  9:41       ` Björn Höfling
2018-12-07 13:30       ` Ludovic Courtès
2018-12-19 12:49         ` Diego Nicola Barbato
2018-12-19 17:37           ` swedebugia
2018-12-19 19:27             ` Tobias Geerinckx-Rice
2018-12-20  5:24               ` swedebugia [this message]
2019-01-18 16:54           ` Ludovic Courtès
2019-01-22 22:07             ` Diego Nicola Barbato
2019-01-23  9:51               ` Ludovic Courtès

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

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

  git send-email \
    --in-reply-to=754f62aa-dd54-4b0e-b78e-052160295af2@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=33647@debbugs.gnu.org \
    --cc=somebody@not-sent-or-endorsed-by.tobias.gr \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.