Re: new manifest format readers?

[Björn Höfling]

On Fri, 09 Jun 2017 14:03:22 +0200
Ricardo Wurmus <address@hidden> wrote:

> Hi Guix,
> 
> I received some feedback on the usability of Guix and one of the
> points I got was about manifests.
> 
> For the simplest case, a user may just want to ask Guix to install
> a fixed set of packages at specified versions.  Currently, doing this
> involves some boilerplate code.
> 
> One can either write a manifest using variable names or convert a list
> of spec strings to a manifest.  The latter case is used a lot at my
> institute and it’s unfortunate that this requires so much code (with
> emphasis on “code”, not on “so much”).
> 
> Here’s an example:
> 
> --8<---------------cut here---------------start------------->8---
> (define packages
>   (list "address@hidden"
>         "address@hidden"
>         "cdogs-sdl"))
> 
> ;; Boilerplate code to turn the above list of packages into a manifest
> (use-modules (gnu packages))
> (packages->manifest (map (compose list specification->package+output)
> packages)) --8<---------------cut
> here---------------end--------------->8---
> 
> It’s not bad, but when a person uses specification strings they really
> just care about the package names and versions.
> 
> Can we simplify this case by adding manifest readers for different
> formats?  One simple format could be plain text:
> 
> --8<---------------cut here---------------start------------->8---
> # this is for compilers
> address@hidden
> address@hidden
> 
> # this is for fun
> cdogs-sdl
> --8<---------------cut here---------------end--------------->8---
> 
> The manifest reader would just discard # comments and interpret each
> non-empty line as a spec string.
> 
> While I love Scheme, I don’t think anything is to be gained from
> exposing users who don’t want to use Scheme for manifests to opaque
> blobs of code and syntax they don’t want to understand.
> 
> What do you think?


Cool :-)

I use Guix for a year now and haven't herd of the Manifests until
recently (contrary to what Mathieu stated), I just use the profile
generational or add my packages to the system-configuration.

I just stumbled over Manifests because I wanted to give Cuirass a try
and there I convert a list of package-strings into a manifest (as
explained in the Guix manual). I really thought how brainfucked this
is, if you are not used to Scheme and returning multiple values. Worse,
if you have one typo in your file, you are confronted with an obscure
stacktrace.

So, definitely a good idea!

And I would like to see it integrated into Cuirass: Currently I have to
prepare a complicated configuration, and a Scheme file that must contain
a function that takes a store (what is that? And why should _I_ care
about that?) and returns a data-structore of ... was it manifests or
derivations or ...

Instead, just give the git repository and a file with packages-list as
you proposed.

Björn