From: kiasoc5 <kiasoc5@disroot.org>
To: Eric Brown <eric.c.brown@mac.com>
Cc: jgart <jgart@dismail.de>, guix-devel@gnu.org
Subject: Re: 🌎️ Install every Guix package 🌎️
Date: Thu, 5 Jan 2023 13:48:55 -0500 [thread overview]
Message-ID: <336ec686-6f54-9d7b-e16f-3c14fd4063f6@disroot.org> (raw)
In-Reply-To: <m2h6x5r8yb.fsf@ecbrown.ericcbrown.com>
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?
next prev parent reply other threads:[~2023-01-05 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 2:33 🌎️ Install every Guix package 🌎️ jgart
2023-01-04 3:09 ` Install every Guix package Nguyễn Gia Phong
2023-01-04 5:39 ` 🌎️ Install every Guix package 🌎️ kiasoc5
2023-01-04 15:52 ` Eric Brown
2023-01-05 2:04 ` 宋文武
2023-01-05 2:50 ` Eric Brown
2023-01-05 18:48 ` kiasoc5 [this message]
2023-01-05 19:01 ` Eric Brown
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=336ec686-6f54-9d7b-e16f-3c14fd4063f6@disroot.org \
--to=kiasoc5@disroot.org \
--cc=eric.c.brown@mac.com \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
/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).