From: Troy Sankey <sankeytms@gmail.com>
To: guix-devel@gnu.org
Subject: updating many haskell packages
Date: Mon, 06 Feb 2017 00:23:23 -0500 [thread overview]
Message-ID: <148635860347.5455.1039513310657824569@what> (raw)
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
I have a WIP branch which contains many haskell package updates and
additions, and makes haskell-build-system use the latest ghc (8.0.2).
https://github.com/pwnage101/guix/tree/add-gitit
It started as a small project to create a Gitit package (hence the name
of the branch), but blew up into something larger. It's hard work, so I
just wanted to check in with you all to see if this seems like the right
direction.
As of this writing, I have over 66 packages updated, 16 added, and
various fixes on existing packages to get everything buildable against
ghc@8.0.2. I'm debating whether I should systematically update all the
haskell packages while I'm at it, or just make sure everything is
buildable under 8.0.2. There are over 277 haskell packages in all.
I wonder how I should send these patches after I'm all done. git
send-email? That seems crazy.
Troy
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEE0zLJ6STd4Cp+CgbIgs677ofYV8IFAliYCEMACgkQgs677ofY
V8KA0Q/+LeWmLqnQRWt04JFtO2v0Vai//JqzESel/Jqs5XmpDltb8R5j3MlbLoLD
88wdrwf3RLlMElYxJtukSap+DWXBDmxZ2u8CkRGxTLXAPTNb/EqcRVRfUaguQ04z
R2nDqeqrm7CpazbiBbpEx3CpSRqYfrGWkAZHZZlNeOqFoSeDT9Tb7TVgj/Z6kmnH
ea9ALO3yYqPdCqqfgsffhixMGGew95ccLG+C9jeMQyLdeszXYkDoRbLV2TRHAt52
myrFdpv1aoDqaVsQs9YIFWalXECsaaFODgw9C1s7BPoTT5pnwb0/SHXKloPPPWom
aX4iIVg9MTuGDDycopfPW0qIpxPcWtZDYYkrUEfpklg+ouVEqCyTPZdcTAt2JBa1
erc35Pk2MjoBGhbSJN30QLqkYYdqGI5lq+dZTfE8kXWcAP1unCn7Z3fvhb9HkA4R
33uScZ56kF/Tm9uBO6eYw0oGt4eVfMdrZfs0AjpDcK3RQ3RtwWH/BQohutHJhbJp
/ARBgWyk9QQA8qHEGdUHjkNkRVi2KJJPqq+Sz380GZBpW50hcGzW12ZRRGVRlhTr
PusvoRtrmYVECcKpNIoNDiM3vdJg2UzYpRKvv36ytMdGumrreBrmRQAvItJFaBW+
3Kyd9Ek7sqlQoUwwy3V+LevRSX7GGHklcq6rqUOjLK4KfcOwbHk=
=As5G
-----END PGP SIGNATURE-----
next reply other threads:[~2017-02-06 5:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 5:23 Troy Sankey [this message]
2017-02-06 15:47 ` updating many haskell packages Leo Famulari
-- strict thread matches above, loose matches on Subject: below --
2017-02-06 8:03 Federico Beffa
2017-02-06 8:13 ` Federico Beffa
2017-02-15 19:07 ` Troy Sankey
2017-02-17 16:43 ` Ricardo Wurmus
2017-02-06 15:23 ` Troy Sankey
2017-02-06 20:34 ` Federico Beffa
2017-02-06 21:00 ` Troy Sankey
2017-02-15 19:31 ` Troy Sankey
2017-02-17 8:00 ` Federico Beffa
2017-02-17 17:47 ` Troy Sankey
2017-02-18 9:43 ` Federico Beffa
2017-02-18 17:40 ` Troy Sankey
2017-02-18 20:23 ` Federico Beffa
2017-02-19 19:21 ` Troy Sankey
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=148635860347.5455.1039513310657824569@what \
--to=sankeytms@gmail.com \
--cc=guix-devel@gnu.org \
/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).