all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: Csepp <raingloom@riseup.net>
Cc: "Simon Tournier" <zimon.toutoune@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Andreas Enge" <andreas@enge.fr>,
	guix-devel@gnu.org
Subject: Re: Faster “guix search” (was Re: How many bytes do we add (closure of guix) when adding one new package?)
Date: Wed, 31 May 2023 11:55:55 +0000	[thread overview]
Message-ID: <NpKgW_AddhjDrHHsN9f8tdXODpHKpYENw2KnstTW91lDZC3gVPHG5ncXd6Zn-9mWchr06z5gEi_Zsh2RK8iOk4NGUcVNmLacd4SUMm3lsAI=@lendvai.name> (raw)
In-Reply-To: <87ttvska4n.fsf@riseup.net>

> It makes zero sense to load full package definitions from disk for
> most queries, such as guix search, with an SoA representation we
> could load only the fields that we care about.


i'd like to quickly point out something while we are discussing this:

when i came to guix it was rather confusing that there two namespaces through which one can get hold of a package object:

1) module-global variables in the scheme module system

2) a reified repository of packages (i.e. a scheme hash table, and some lookup functions).

these two namespaces are quite indepenedent from each other, and there are no formal rules that govern the relationship between the two.

there are scheme variable reference in some places, some others issue a call to SPECIFICATION->PACKAGE, manifests do that implicitly (?), etc. my gut feeling is that there is potential here for unification and simplification, without limiting composability.

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“The greatest gift you can give someone is your own personal development. I used to say, 'If you’ll take care of me, I’ll take care of you'. Now I say, 'I will take care of me for you, if you will take care of you for me'.”
	— Jim Rohn



  reply	other threads:[~2023-05-31 11:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 10:13 bug#63050: "guix pull" requires graphical libraries Andreas Enge
2023-04-25 21:48 ` Ludovic Courtès
2023-04-26  7:28   ` Andreas Enge
2023-04-26  8:45     ` Josselin Poiret via Bug reports for GNU Guix
2023-04-26 16:59       ` Liliana Marie Prikler
2023-04-26 17:25         ` Andreas Enge
2023-04-26 18:39           ` Josselin Poiret via Bug reports for GNU Guix
2023-04-26 19:21             ` Andreas Enge
2023-04-26 19:34             ` Liliana Marie Prikler
2023-04-28 15:18   ` Simon Tournier
2023-05-03 19:33     ` Ludovic Courtès
2023-05-04  8:56       ` Simon Tournier
2023-05-05 15:21         ` Csepp
2023-05-09 12:36           ` Simon Tournier
2023-05-11 21:30             ` Csepp
2023-05-03 19:50   ` bug#63050: Reducing the closure size of Graphviz Ludovic Courtès
2023-05-04  9:00     ` Simon Tournier
2023-05-20 16:12     ` bug#63050: "guix pull" requires graphical libraries Ludovic Courtès
2023-05-20 16:38       ` Andreas Enge
2023-05-24 13:10         ` Ludovic Courtès
2023-05-25 18:24           ` How many bytes do we add (closure of guix) when adding one new package? Simon Tournier
2023-05-26 16:21             ` Ludovic Courtès
2023-05-30 12:10               ` Simon Tournier
2023-05-30 19:10                 ` Csepp
2023-05-31  8:05                   ` Faster “guix search” (was Re: How many bytes do we add (closure of guix) when adding one new package?) Simon Tournier
2023-05-31 11:10                     ` Csepp
2023-05-31 11:55                       ` Attila Lendvai [this message]
2023-05-30 20:55                 ` How many bytes do we add (closure of guix) when adding one new package? Jack Hill
2023-05-31  8:27                   ` Simon Tournier
2023-05-31 12:47                     ` Guillaume Le Vaillant

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='NpKgW_AddhjDrHHsN9f8tdXODpHKpYENw2KnstTW91lDZC3gVPHG5ncXd6Zn-9mWchr06z5gEi_Zsh2RK8iOk4NGUcVNmLacd4SUMm3lsAI=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=raingloom@riseup.net \
    --cc=zimon.toutoune@gmail.com \
    /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.