Hello, Ludovic Courtès <[email protected]> writes:
> Daniel Littlewood <[email protected]> skribis: > >> Something I did not see anybody else mention, and I am not completely >> sure of my facts here, but doesn't guix's packaging model lean rather >> heavily on packages being source code? More than other package >> ecosystems, I mean. Since a guix package is a scheme object, which can >> refer to data across modules, naively putting this text into a >> database would not work. By comparison if your package registry is a >> bunch of JSON files then it is straightforward to migrate that from >> git to a database. > > Yes, you’re right: Git and packages-as-source-code are at the heart of > Guix. > > But, if we wanted to, we could create a “dead” representation of our > packages (think: pure data, like a JSON file or SQL database) that would > be good enough for certain operations like “guix install foo”. That > representation could coexist with the actual source as we know it. (And > the actual source would still be needed for many other operations.) Using a database would not necessarily mean storing packages as pure data. Databases can store source code as text and byte code as byte array. However with that option the question is how to compile/load such form of code. Mathieu
