unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Timothy Sample <samplet@ngyro.com>
To: Robert Vollmert <rob@vllmrt.net>
Cc: guix-devel@gnu.org
Subject: Re: haskell changes
Date: Sun, 18 Aug 2019 21:09:30 -0400	[thread overview]
Message-ID: <87d0h22c6t.fsf@ngyro.com> (raw)
In-Reply-To: <87imqw3lyf.fsf@ngyro.com> (Timothy Sample's message of "Fri, 16 Aug 2019 16:16:24 -0400")

Hi Robert,

Timothy Sample <samplet@ngyro.com> writes:

> Robert Vollmert <rob@vllmrt.net> writes:
>
>> I have some Haskell-related changes ready for review and ideally merge
>> on wip-haskell-updates.
>
> Sounds good.  I’ll take a look at that branch soon.
>
>> Changes are:
>> 1. move libraries out of haskell.scm (mostly into haskell-xyz.scm, those
>> without ghc- prefix into haskell-apps.scm), as per
>> https://lists.gnu.org/archive/html/guix-devel/2019-07/msg00070.html

There’s a bit too much going on this commit.  Would it be possible to
make the first commit do nothing but delete packages from “haskell.scm”
and move them to the “apps”, “check”, and “xyz” modules, and update the
module references?  Then, you can have another commit to move the SDL
packages from “apps” to “xyz”, and another for the module commentaries.
This way, it will be a lot easier to see what’s going on.

Also, it looks like you’ve reordered some packages in “haskell-xyz” in
this commit, too.  I agree with Ricardo that it’s probably best to leave
the ordering alone, but if it needs to be done, it should be it’s own
commit.

About the commit message, you don’t need to write each variable name out
twice.  You can group all the files that have updated module references,
too.  See commit 0791437f972caa7e48de91ad5cb150a614f617c2 for Ricardo’s
message when moving the Guile packages into “guile-xyz”.  I don’t think
you need the “[A]s discussed on guix-devel” part, but if you want to
keep it, you should provide a link to the discussion.

I know last time I made a lot of fixes myself, but I’m hoping this
feedback is useful for getting a better feel for Guix’s conventions.
Let me know if you feel differently.  :)


-- Tim

      reply	other threads:[~2019-08-19  1:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 17:57 haskell changes Robert Vollmert
2019-08-16 18:07 ` Ricardo Wurmus
2019-08-16 18:14   ` Robert Vollmert
2019-08-16 20:16 ` Timothy Sample
2019-08-19  1:09   ` Timothy Sample [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0h22c6t.fsf@ngyro.com \
    --to=samplet@ngyro.com \
    --cc=guix-devel@gnu.org \
    --cc=rob@vllmrt.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).