From: "Edison Ibáñez" <arkhan@disroot.org>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: help-guix@gnu.org
Subject: Re: Update Xonsh
Date: Wed, 20 May 2020 14:34:35 -0500 [thread overview]
Message-ID: <87k116o0xg.fsf@disroot.org> (raw)
In-Reply-To: <87imgruplq.fsf@zancanaro.id.au>
Thanks for the help, I just saw that they updated xonsh to the
latest version
El miércoles 20 de mayo del 2020 a las 0045 horas, Carlo Zancanaro
escribió:
> Hey Edison,
>
> One easy way to do this is to just put your package definition
> in
> config.scm, above your operating system definition. I haven't
> tried it with a shell, but the basic idea would be to have
> something
> like this:
>
> (define-public xonsh
> ... your package definition ...)
>
> (operating-system
> ... other bits ...
> (users (cons (user-account
> ... other bits ...
> (shell (file-append xonsh "/bin/xonsh")))
> %base-user-accounts))
> ... other bits ...)
>
> Another way to do it would be to submit a patch updating xonsh
> to be
> included in Guix, which would also benefit all other Guix users.
>
> Carlo
>
> On Wed, May 20 2020, Edison Ibáñez wrote:
>> Regards,
>>
>> I currently use xonsh as my user's shell, but the default
>> version in
>> GuixSD is 0.6.2 and the latest available is 0.9.18.
>>
>> I wrote a file to install the latest version of this package
>> but I
>> cannot set this version as my user's default shell.
>>
>> There is a way to update xonsh in the config.scm file to the
>> latest
>> available version.
>>
>> Thank you
>>
>> – Edison Ibáñez
>> One Emacs to rule them all
next prev parent reply other threads:[~2020-05-20 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 0:31 Edison Ibáñez
2020-05-20 3:03 ` Update Xonsh Edison Ibáñez
2020-05-20 5:45 ` Carlo Zancanaro
2020-05-20 19:34 ` Edison Ibáñez [this message]
2020-05-20 20:17 ` Tobias Geerinckx-Rice
2020-05-21 20:39 ` Edison Ibáñez
2020-05-24 16:41 ` Josh Marshall
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=87k116o0xg.fsf@disroot.org \
--to=arkhan@disroot.org \
--cc=carlo@zancanaro.id.au \
--cc=help-guix@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.
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).