[bug#39625] [PATCH] website: Update Guix manifest.

[sirgazil via Guix-patches via <guix-patches@gnu.org>]

 ---- On Fri, 24 Jul 2020 20:54:10 -0500 Brett Gilio <brettg@gnu.org> wrote ----
 > sirgazil <sirgazil@zoho.com> writes:
 > 
 > >  
 > > -(use-modules (guix profiles)
 > > -         (gnu packages))
 > > +(use-modules (gnu packages))
 > 
 > I think manifests require the (guix profiles) module.

Hmm, my manifests work without importing "(guix profiles)".

This was a long time ago, but the reason I imported that module is that in the beginning I was thinking on providing a manifest that would create a profile generation that was the union of the packages installed in the current user profile plus the packages required to develop the website. I was going to use "(profile-manifest %user-profile-directory)" for that, which comes from "(guix profiles)". But that was before I knew you could use different Guix profiles for different projects instead of polluting your user profile, so I changed my mind and forgot to delete "(guix profiles)".


 > > -(define dev-packages
 > > -  (list "glibc-locales"
 > > -    "guile@2.2"
 > > -    "guile-syntax-highlight"
 > > -    "guix"
 > > -    "haunt"))
 > > -
 > > -
 > > -(map specification->package dev-packages)
 > > +(specifications->manifest
 > > + (list "git"
 > > +       "glibc-locales"
 > > +       "gnutls"
 > > +       "guile"
 > > +       "guile-json"
 > > +       "guile-syntax-highlight"
 > > +       "guix"
 > > +       "haunt"))
 > 
 > Could I inquire why you opted to remove the function for dev-packages?
 > :)

I was thinking on separating package requirements with variables such as "dev-packages", "test-packages", "production-packages", etc., but then I thought it was unnecessary at this point because the website does not currently have that many requirements...