🌎️ Install every Guix package 🌎️

🌎️ Install every Guix package 🌎️

[jgart]

Hi Guixers,

How would you approach writing a script that installs every Guix package exhaustively for your current revision?

I'm thinking of something similar to `all-packages` on PyPi but for every Guix package (the whole wide 🌎️).

https://pypi.org/project/all-packages/

Re: Install every Guix package

[Nguyễn Gia Phong]

On 2023-01-04 at 02:33+00:00, jgart wrote:
> How would you approach writing a script that installs
> every Guix package exhaustively for your current revision?

I don't want to know why you'd like to do that,
but you can start from here:

repo=https://data.guix.gnu.org/repository/1/branch/master
path=latest-processed-revision/packages.json
guix shell curl -- curl $repo/$path?all_results=on |
  guix shell jq -- jq -r '.packages[] | .name' |
  guix shell findutils -- xargs guix shell

Re: 🌎️ Install every Guix package 🌎️

[kiasoc5]

On 1/3/23 21:33, jgart wrote:
> Hi Guixers,
> 
> How would you approach writing a script that installs every Guix package exhaustively for your current revision?
> 
> I'm thinking of something similar to `all-packages` on PyPi but for every Guix package (the whole wide 🌎️).
> 
> https://pypi.org/project/all-packages/
> 

Perhaps you are inspired by this?

https://a.exozy.me/posts/installing-every-arch-package/

I'd run the list of all packages by guix size before attempting such 
shenanigans (untested):

```
$ guix package -A | cut -f 1 | sort -u | xargs guix size
```

Surely if there are outstanding questions that could be answered by 
installing all packages, they could be answered in another way?

Re: 🌎️ Install every Guix package 🌎️

[Eric Brown]

kiasoc5 <kiasoc5@disroot.org> writes:

> Surely if there are outstanding questions that could be answered by installing
> all packages, they could be answered in another way?

I do this to keep packages as reasonably close to "locked and loaded" as
possible (including all external channels) so that when I need them
interactively, they are ready on my system.

It's easier and less trouble than Cuirass, in my view.

Re: 🌎️ Install every Guix package 🌎️

[宋文武]

"jgart" <jgart@dismail.de> writes:

> Hi Guixers,
>
> How would you approach writing a script that installs every Guix package exhaustively for your current revision?
>
> I'm thinking of something similar to `all-packages` on PyPi but for every Guix package (the whole wide 🌎️).
>
> https://pypi.org/project/all-packages/


Maybe guix package -m manifest.scm:

--8<---------------cut here---------------start------------->8---
(use-modules
 (srfi srfi-1)
 (ice-9 match)
 (gnu packages)
 (guix packages))

;;; copied from guix/scripts/weather.scm.
(define (all-packages)
  "Return the list of public packages we are going to query."
  (delete-duplicates
   (fold-packages (lambda (package result)
                    (match (package-replacement package)
                      ((? package? replacement)
                       (cons* replacement package result))
                      (#f
                       (cons package result))))
                  '()

                  ;; Dismiss deprecated packages but keep hidden packages.
                  #:select? (negate package-superseded))
   eq?))

(packages->manifest (all-packages))
--8<---------------cut here---------------end--------------->8---

No idea how long it will be :)

Re: 🌎️ Install every Guix package 🌎️

[Eric Brown]

"jgart" <jgart@dismail.de> writes:

> Hi Guixers,
>
> How would you approach writing a script that installs every Guix package exhaustively for your current revision?
>
> I'm thinking of something similar to `all-packages` on PyPi but for every Guix package (the whole wide 🌎️).
>
> https://pypi.org/project/all-packages/

guix package -A | cut -f 1 | sort -u | xargs guix build --keep-going

can accomplish this. The `--keep-going' flag is useful in case a package
does not build.

Occasionally, I will sandwich in a negated grep to
exclude packages:

guix package -A | cut -f 1 | sort -u | grep -v "emacs-guile" | xargs guix build --keep-going

(Aside: emacs-guile-on-guix-system is the pinnacle of GNU, IMO but it failed to
build--appearing to be abandoned--and was removed.)

One may also select just the packages they want, perhaps by using a
scripting language such as python to make larger selections more
convenient.

This can be combined with a substitute server and an offload build
machine to make an on-site cache. One can choose whether to employ the
Guix substitute servers if that would be beneficial.

Re: 🌎️ Install every Guix package 🌎️

[kiasoc5]

On 1/4/23 21:50, Eric Brown wrote:
> "jgart" <jgart@dismail.de> writes:
> 
>> Hi Guixers,
>>
>> How would you approach writing a script that installs every Guix package exhaustively for your current revision?
>>
>> I'm thinking of something similar to `all-packages` on PyPi but for every Guix package (the whole wide 🌎️).
>>
>> https://pypi.org/project/all-packages/
> 
> guix package -A | cut -f 1 | sort -u | xargs guix build --keep-going
> 
> can accomplish this. The `--keep-going' flag is useful in case a package
> does not build.
> 
> Occasionally, I will sandwich in a negated grep to
> exclude packages:
> 
> guix package -A | cut -f 1 | sort -u | grep -v "emacs-guile" | xargs guix build --keep-going
> 
> (Aside: emacs-guile-on-guix-system is the pinnacle of GNU, IMO but it failed to
> build--appearing to be abandoned--and was removed.)
> 
> One may also select just the packages they want, perhaps by using a
> scripting language such as python to make larger selections more
> convenient.
> 
> This can be combined with a substitute server and an offload build
> machine to make an on-site cache. One can choose whether to employ the
> Guix substitute servers if that would be beneficial.
> 
I just realized that this downloads all packages into the store, which 
not the same as installing all the packages into one or many profiles. I 
wonder what the minimum set of profiles to install all packages while 
avoiding collisions might be?

Re: 🌎️ Install every Guix package 🌎️

[Eric Brown]

kiasoc5 <kiasoc5@disroot.org> writes:

> I just realized that this downloads all packages into the store, which not the
> same as installing all the packages into one or many profiles. I wonder what the
> minimum set of profiles to install all packages while avoiding collisions might
> be?

Correct, my reply was about building everything rather than installing
everything.

But--as a case merely to prove a point--if you include the kernel in the required set
of packages, then the single set of non-colliding packages can not be
defined because there are several mutually-exclusive kernels.

A valid "maximum coverage" set must have some additional constraints.