Am I doing it all wrong?

Am I doing it all wrong?

[jgart]

Hi,

This is what I do to work on GNU Guix on a foreign distro:

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

cd guix
guix shell -D guix --container -- ./bootstrap
guix shell -D guix --container -- ./configure --localstatedir=/var
guix shell -D guix --container -- make
guix shell --container --network coreutils vis ripgrep rlwrap -D guix --share=/var/guix/

Should I be doing anything differently in the above for setting up a dev environment for guix hacking?

--
jgart

Re: Am I doing it all wrong?

[Ricardo Wurmus]

jgart <jgart@dismail.de> writes:

> Hi,
>
> This is what I do to work on GNU Guix on a foreign distro:
>
> git clone https://git.savannah.gnu.org/git/guix.git
>
> cd guix
> guix shell -D guix --container -- ./bootstrap
> guix shell -D guix --container -- ./configure --localstatedir=/var
> guix shell -D guix --container -- make
> guix shell --container --network coreutils vis ripgrep rlwrap -D guix --share=/var/guix/
>
> Should I be doing anything differently in the above for setting up a dev environment for guix hacking?

Why do you keep exiting and entering the container for each command?
And: why use a container at all when “guix shell --pure” would be more
than enough?

I’d just start a new shell *once* and then run the commands inside of
the shell session.

-- 
Ricardo

Re: Am I doing it all wrong?

[jgart]

On Sat, 27 Aug 2022 19:15:24 +0200 Ricardo Wurmus <rekado@elephly.net> wrote:

> Why do you keep exiting and entering the container for each command?

I agree. I think I had some issue iirc trying to run them all in one command with &&

> And: why use a container at all when “guix shell --pure” would be more
> than enough?

Because I'm running Guix on void linux and here be dragons I don't yet understand.

> I’d just start a new shell *once* and then run the commands inside of
> the shell session.

I was running the above commands as part of this shell script:

https://git.sr.ht/~whereiseveryone/dot/tree/master/item/bin/executable_guix-prepare-tree

Thanks for the feedback. Much appreciated!

--
jgart

Re: Am I doing it all wrong?

[(]

Hello jgart,

On Sat Aug 27, 2022 at 4:34 PM BST, jgart wrote:
> guix shell -D guix --container -- make

You can use `make -j$(nproc)` to make the build *much* faster.

    -- (

Re: Am I doing it all wrong?

[(]

On Sat Aug 27, 2022 at 7:38 PM BST, jgart wrote:
> I agree. I think I had some issue iirc trying to run them all in one command with &&

Perhaps:

  guix shell -D guix --pure -- sh -c "./bootstrap && ./configure --localstatedir=/var && make -j$(nproc)"

    -- (

Re: Am I doing it all wrong?

[(]

On Sat Aug 27, 2022 at 7:38 PM BST, jgart wrote:
> I agree. I think I had some issue iirc trying to run them all in one command with &&

Or maybe...

  guix shell -D guix -- sh <<EOF
  ./bootstrap && ./configure --localstatedir=/var && make -j$(nproc)
  EOF

    -- (

Re: Am I doing it all wrong?

[(]

On Sat Aug 27, 2022 at 9:56 PM BST, ( wrote:
>   guix shell -D guix -- sh <<EOF
>   ./bootstrap && ./configure --localstatedir=/var && make -j$(nproc)
>   EOF

You could wrap it in a sh function:

  gsh() {
      guix shell $@ -- sh
  }

  gsh -D guix <<EOF
  ./bootstrap && ./configure --localstatedir=/var && make -j$(nproc)
  EOF

    -- (

Re: Am I doing it all wrong?

[Csepp]

"(" <paren@disroot.org> writes:

> On Sat Aug 27, 2022 at 9:56 PM BST, ( wrote:
>>   guix shell -D guix -- sh <<EOF
>>   ./bootstrap && ./configure --localstatedir=/var && make -j$(nproc)
>>   EOF
>
> You could wrap it in a sh function:
>
>   gsh() {
>       guix shell $@ -- sh
>   }
>
>   gsh -D guix <<EOF
>   ./bootstrap && ./configure --localstatedir=/var && make -j$(nproc)
>   EOF
>
>     -- (

Did you test that one?  Because I'm pretty sure it won't work, you
aren't passing the heredoc file descriptor to sh but guix shell.
Also, that should probably be "$@", just in case.

Because Bash is garbage. :)

Re: Am I doing it all wrong?

[Csepp]

jgart <jgart@dismail.de> writes:

> Hi,
>
> This is what I do to work on GNU Guix on a foreign distro:
>
> git clone https://git.savannah.gnu.org/git/guix.git
>
> cd guix
> guix shell -D guix --container -- ./bootstrap
> guix shell -D guix --container -- ./configure --localstatedir=/var
> guix shell -D guix --container -- make
> guix shell --container --network coreutils vis ripgrep rlwrap -D guix --share=/var/guix/
>
> Should I be doing anything differently in the above for setting up a dev environment for guix hacking?

You probably want to invoke ./configure like so:
./configure --sysconfdir=/etc/ --localstatedir=/var/

Otherwise if you reconfigure the system from the local checkout you will
run into some "fun" behaviour.

Re: Am I doing it all wrong?

[(]

On Sun Aug 28, 2022 at 12:50 PM BST, Csepp wrote:
> Did you test that one?  Because I'm pretty sure it won't work, you
> aren't passing the heredoc file descriptor to sh but guix shell.

I hadn't tested it then, but I just did now, and it works.

  gsh -D guix lua <<EOF
  echo "hello"
  lua -e 'print "hello"'
  guile -c '(display "hello") (newline)'
  EOF
  hello
  hello
  hello

> Also, that should probably be "$@", just in case.

I don't think it'll make any difference; if, say, "foo" "bar" "baz" is
passed, both $@ and "$@" will expand to "foo" "bar" "baz" (yes, bypassing
the quotes).

According to POSIX.1-2017's specification of `sh`:

  When the expansion occurs within double-quotes, the behavior is unspecified
  unless one of the following is true:

  + Field splitting [...] would be performed if the expansion were not within
    double-quotes [...].

  + [...]

So, $@ == "$@".

> Because Bash is garbage. :)

I can't disagree on that one. :)

    -- (

Re: Am I doing it all wrong?

[Saku Laesvuori]

[-- Attachment #1: Type: text/plain, Size: 760 bytes --]

> > Also, that should probably be "$@", just in case.
> 
> I don't think it'll make any difference; if, say, "foo" "bar" "baz" is
> passed, both $@ and "$@" will expand to "foo" "bar" "baz" (yes, bypassing
> the quotes).
> 
> According to POSIX.1-2017's specification of `sh`:
> 
>   When the expansion occurs within double-quotes, the behavior is unspecified
>   unless one of the following is true:
> 
>   + Field splitting [...] would be performed if the expansion were not within
>     double-quotes [...].
> 
>   + [...]
> 
> So, $@ == "$@".

It does actually make a difference if the arguments have spaces. Given
arguments "foo" and "foo bar", $@ expands to "foo" "foo" "bar" and "$@"
expands to "foo" "foo bar".

- Saku Laesvuori

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]