From: Apoorv via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
Tobias Geerinckx-Rice <me@tobias.gr>,
Ekaitz Zarraga <ekaitz@elenq.tech>
Subject: Re: Suggestion for a guix shell feature.
Date: Mon, 1 Jan 2024 04:01:16 +0100 (CET) [thread overview]
Message-ID: <Nn1xycJ--3-9@tuta.io> (raw)
In-Reply-To: <87o7e6pb00.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
I can add rust:cargo but the package definition in the guix.scm is already using `cargo-build-system` shouldn't it include rust and cargo etc automatically?
--
Sent with Tuta; enjoy secure & ad-free emails:
https://tuta.com
Dec 31, 2023, 16:56 by maxim.cournoyer@gmail.com:
> Hi,
>
> Apoorv <apoorvs@tuta.io> writes:
>
>> Sorry, this is my first time using some mailing list.
>>
>> I tried using `--container` and `--emulate-fhs` first it doesn't seem
>> to use `guix.scm` automatically I have to specify it using
>> `--file=guix.scm`. Second, the container is missing so much more stuff
>> like cargo for example.
>>
>
> Yes, that's a somewhat surprising behavior designed to avoid bad
> surprises, in that if you start using arguments with 'guix shell', the
> 'do what I mean' magic is cancelled and you need to explicit each
> arguments.
>
> About cargo missing, what prevents you from adding rust:cargo to your
> guix.scm file?
>
>> This is my own project in Rust lang, I basically define `guix.scm` for
>> all my projects since I started using Guix.
>>
>
> I guess this being rust everything is statically compiled, and the usual
> dynamic loader is not useful here (the RUNPATH baked in elf binaries is
> not used).
>
> --
> Thanks,
> Maxim
>
[-- Attachment #2: Type: text/html, Size: 2023 bytes --]
next prev parent reply other threads:[~2024-01-04 20:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NmrVHaU--3-9@tuta.io>
2023-12-30 3:10 ` Suggestion for a guix shell feature Maxim Cournoyer
2023-12-31 12:10 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2023-12-31 16:55 ` Maxim Cournoyer
2024-01-01 3:01 ` Apoorv via Development of GNU Guix and the GNU System distribution. [this message]
2024-01-02 16:33 ` Maxim Cournoyer
2024-01-03 9:14 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2024-01-03 17:57 ` Maxim Cournoyer
2024-01-05 13:38 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2023-12-21 16:10 Apoorv via Development of GNU Guix and the GNU System distribution.
2023-12-29 3:58 ` Maxim Cournoyer
2023-12-29 13:50 ` Ekaitz Zarraga
2023-12-29 15:39 ` Tobias Geerinckx-Rice
2023-12-29 17:21 ` Maxim Cournoyer
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=Nn1xycJ--3-9@tuta.io \
--to=guix-devel@gnu.org \
--cc=apoorvs@tuta.io \
--cc=ekaitz@elenq.tech \
--cc=maxim.cournoyer@gmail.com \
--cc=me@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 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).