Re: Guix wiki

[Attila Lendvai <attila@lendvai.name>]

here's an example of what i would add to the wiki, because i think all other options are worse (but correct me if i'm wrong!):

open a page about highlevel design goals/issues, and then open an entry for the problem that packages have two names in two namespaces: the scheme module/variable namespace, and the guix package name namespace.

these names are pretty much independent from each other (modulo some conventions), and this is an issue for the importers. more specifically the go importer, that currently needs scheme variable names to refer to the identified dependencies, while it can only look up the package objects. these objects know nothing about the scheme variables they are stored in.

if someone wants to use guix as a platform for reproducible builds of go projects (independent of guix revisions), then a package definitions is needed that refers to specific versions of its dependencies.

currently it's not possible to open a new isolated scheme module, and algorithmically define/import the entire transitive closure of the dependencies of a go project, because they may clash in the package-name namespace with projects already defined elsewhere in guix.

--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“It's better to know nothing than to know what ain't so.”
	— Josh Billings