From: Adam <adam.quandour@gmail.com>
To: Felix Lechner <felix.lechner@lease-up.com>, help-guix@gnu.org
Subject: Fwd: Is guix the right tool to get package definitions?
Date: Mon, 22 Apr 2024 15:34:38 -0700 [thread overview]
Message-ID: <CA+jnL0Mof-AggHd4kYwZ7xgNow0CiJhRNy-d6BbaDQ7w_N+oQQ@mail.gmail.com> (raw)
In-Reply-To: <CA+jnL0PRgGJ6bWW9D2o4Hx1HwsTYM9yOj7jk01PLhTATXcW=Lg@mail.gmail.com>
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?
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
next prev parent reply other threads:[~2024-04-30 22:52 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 ` Adam [this message]
2024-05-01 14:14 ` Fwd: " Tomas Volf
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+jnL0Mof-AggHd4kYwZ7xgNow0CiJhRNy-d6BbaDQ7w_N+oQQ@mail.gmail.com \
--to=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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.