From: Adam <adam.quandour@gmail.com>
To: help-guix@gnu.org
Subject: Is guix the right tool to get package definitions?
Date: Mon, 22 Apr 2024 16:59:31 +0300 [thread overview]
Message-ID: <CA+jnL0Nq9adRte883dBokY1V=RLqUb_pZio2ARW-akZXGjE_bQ@mail.gmail.com> (raw)
Hi guix!
Recently I used nixos on one of my machines. And I noticed people
there use tar balls for fetching package definitions. And It worked
much faster for me.
That was surprising and I decided to write this letter.
Is git the right tool for getting new package definitions? What if git
commits history will become enormous?
As I see, the first guix pull is running too long for a lot of people.
Probably, there are ways to cache all of this.
Anyway, I'm just curious about it. If there are already answers for my
question, I would like to read them.
next reply other threads:[~2024-04-22 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 13:59 Adam [this message]
2024-04-22 18:40 ` Is guix the right tool to get package definitions? 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
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='CA+jnL0Nq9adRte883dBokY1V=RLqUb_pZio2ARW-akZXGjE_bQ@mail.gmail.com' \
--to=adam.quandour@gmail.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).