Single channel update (or channels vs. GUIX_PACKAGE_PATH)

Single channel update (or channels vs. GUIX_PACKAGE_PATH)

[Pierre Neidhardt]

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

Hi again :)

I was discussing "channels in practice" with Zimoun and we were asking
ourselves: Can we pull a specific channel without pulling
%default-channels?

If not, is there a convenient way to edit+test the package definitions
in local channels?

Maybe I'm missing the obvious?

--
Pierre Neidhardt
https://ambrevar.xyz/

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

Re: Single channel update (or channels vs. GUIX_PACKAGE_PATH)

[John Soo]

Hello Pierre,

I’ve been working a lot on some packages in a private channels and my workflow is usually focused on building properly which is a matter of:

guix build -L /path/to/channel <package>

To test runtime behavior I still have to pull which does mean pulling the default channel, too.  This so far has worked well. If pulling becomes too much, maybe specifying a commit of the default guix channel could work. What do you think?

- John



> On Feb 4, 2019, at 3:16 PM, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> 
> Hi again :)
> 
> I was discussing "channels in practice" with Zimoun and we were asking
> ourselves: Can we pull a specific channel without pulling
> %default-channels?
> 
> If not, is there a convenient way to edit+test the package definitions
> in local channels?
> 
> Maybe I'm missing the obvious?
> 
> --
> Pierre Neidhardt
> https://ambrevar.xyz/

Re: Single channel update (or channels vs. GUIX_PACKAGE_PATH)

[Pierre Neidhardt]

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

Yes, that would work.  I tried something like the following:

--8<---------------cut here---------------start------------->8---
(list (channel
        (name 'guix-chromium)
        (url "https://gitlab.com/mbakke/guix-chromium.git")
        (branch "master"))
       (channel
        (name 'guix)
        (url "https://git.savannah.gnu.org/git/guix.git")
        (branch "master")
        (commit "1d4c2dabefdc5e957ed74a58066f8faa8e0fb70e")))
--8<---------------cut here---------------end--------------->8---

Is there a way to inherit or modify %default-channels to avoid all the
copy-pasting?

Also do you know how to get the last guix generation commit?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

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

Re: Single channel update (or channels vs. GUIX_PACKAGE_PATH)

[Ricardo Wurmus]

Pierre Neidhardt <mail@ambrevar.xyz> writes:

> Is there a way to inherit or modify %default-channels to avoid all the
> copy-pasting?

It’s just a list.  You can cons onto it.

-- 
Ricardo

Re: Single channel update (or channels vs. GUIX_PACKAGE_PATH)

[Pierre Neidhardt]

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


Ricardo Wurmus <rekado@elephly.net> writes:
> It’s just a list.  You can cons onto it.

What I meant is that it does not seem possible to

--8<---------------cut here---------------start------------->8---
(list (channel
       (inherit %default-channels
			 (commit "..."))))
--8<---------------cut here---------------end--------------->8---

Or even

  (set-channel-commit %default-channels "...")

But maybe it's not worth it considering it's only 4 lines.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

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

Re: Single channel update (or channels vs. GUIX_PACKAGE_PATH)

[Ludovic Courtès]

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> Ricardo Wurmus <rekado@elephly.net> writes:
>> It’s just a list.  You can cons onto it.
>
> What I meant is that it does not seem possible to
>
> (list (channel
>        (inherit %default-channels
> 			 (commit "..."))))
>
> Or even
>
>   (set-channel-commit %default-channels "...")
>
> But maybe it's not worth it considering it's only 4 lines.

‘%default-channels’ is a list, not a <channel> record, so what you
suggest above cannot work.

But you can do:

  (list (channel
          (inherit (first %default-channels))
          …))

That’s what the stable-channel trick I posted does.

Ludo’.

Re: Single channel update (or channels vs. GUIX_PACKAGE_PATH)

[Pierre Neidhardt]

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

Damn, my bad, I completely missed the obvious here.  Thanks for answering this, Ludo!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

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

Re: Single channel update (or channels vs. GUIX_PACKAGE_PATH)

[Chris Marusich]

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

John Soo <jsoo1@asu.edu> writes:

> I’ve been working a lot on some packages in a private channels and my
> workflow is usually focused on building properly which is a matter of:
>
> guix build -L /path/to/channel <package>

FYI, I believe you can also specify local paths in the channel
description file, itself, either by saying "file:///path/to/channel" or
"/path/to/channel" - I can't remember which.

-- 
Chris

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