From: Tomas Volf <~@wolfsden.cz>
To: Adam <adam.quandour@gmail.com>
Cc: Felix Lechner <felix.lechner@lease-up.com>, help-guix@gnu.org
Subject: Re: Fwd: Is guix the right tool to get package definitions?
Date: Wed, 1 May 2024 16:14:19 +0200 [thread overview]
Message-ID: <ZjJOOybKHklRdf0E@ws> (raw)
In-Reply-To: <CA+jnL0Mof-AggHd4kYwZ7xgNow0CiJhRNy-d6BbaDQ7w_N+oQQ@mail.gmail.com>
[-- 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 --]
prev parent reply other threads:[~2024-05-01 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 13:59 Is guix the right tool to get package definitions? Adam
2024-04-22 18:40 ` Felix Lechner via
[not found] ` <CA+jnL0PRgGJ6bWW9D2o4Hx1HwsTYM9yOj7jk01PLhTATXcW=Lg@mail.gmail.com>
2024-04-22 22:34 ` Fwd: " Adam
2024-05-01 14:14 ` Tomas Volf [this message]
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=ZjJOOybKHklRdf0E@ws \
--to=~@wolfsden.cz \
--cc=adam.quandour@gmail.com \
--cc=felix.lechner@lease-up.com \
--cc=help-guix@gnu.org \
/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.
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).