Re: Fwd: Is guix the right tool to get package definitions?

[Tomas Volf <~@wolfsden.cz>]

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

On 2024-04-22 15:34:38 -0700, Adam wrote:
> forgot to cc to help guix
>
> ---------- Forwarded message ---------
> From: Adam <adam.quandour@gmail.com>
> Date: Mon, Apr 22, 2024 at 1:56 PM
> Subject: Re: Is guix the right tool to get package definitions?
> To: Felix Lechner <felix.lechner@lease-up.com>
>
>
> Sure, so my concern is - will it be difficult to guix pull new package
> definitions when git commit history of guix channel will become
> enormous? Is there any way to cache git commit history? Or maybe there
> are other ways to achieve this?

The git repository with packages is cached, in ~/.cache/guix/checkouts I
believe.  So after the initial guix pull, subsequent invocations do not spent
much time on the git pull part.

>
> On Mon, Apr 22, 2024 at 11:40 AM Felix Lechner
> <felix.lechner@lease-up.com> wrote:
> >
> > Hi Adam,
> >
> > On Mon, Apr 22 2024, Adam wrote:
> >
> > > Anyway, I'm just curious about it. If there are already answers for my
> > > question, I would like to read them.
> >
> > I am not familiar with the tarballs Nix uses to deliver updates of
> > package definitions.  Their repo is probably bigger than Guix.  Here, we
> > use 'guix pull' together with channel definitions.
> >
> > Is there a chance you might rephrase your question for a better answer,
> > please?
> >
> > Kind regards
> > Felix
>

--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

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