From: Troy Sankey <sankeytms@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: updating many haskell packages
Date: Wed, 15 Feb 2017 14:31:30 -0500 [thread overview]
Message-ID: <148718709098.32672.6688568200387118544@what> (raw)
In-Reply-To: <148641482905.2874.1459989202091260937@what>
[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]
Quoting Troy Sankey (2017-02-06 16:00:29)
> Quoting Federico Beffa (2017-02-06 15:34:47)
> > I would consider a discrepancy between a cabal file on Hackage and the
> > actual cabal file included in a tar archive a bug. It may be helpful
> > to report it to the author.
>
> I found this issue on the hackage github:
>
> https://github.com/haskell/hackage-server/issues/503
>
> It looks like it's a feature of hackage and/or cabal to allow multiple
> revisions of cabal files per tarball release. IIUC, the `cabal get`
> utility takes care of automatically updating the cabal file to the
> latest revision.
>
> I'll have to look more into this later.
Indeed the .cabal files can be revised between releases. Somehow the
new revisions get pushed to the all-cabal-files repository [0] with an
additional "x-revision" key [1], and Hackage picks up the new cabal
file. The `cabal` and `stack` utilities substitute the .cabal file from
the release tarball with the revised .cabal file from Hackage if it is
newer.
In theory, anything in the .cabal file could be modified, not just
dependency bounds. I think guix should use the updated .cabal files for
better consistency with the rest of the haskell ecosystem, and also for
less per-package maintenance cost.
How can guix adapt? Should we somehow incorporate the all-cabal-files
repository in the haskell build system, adding a post-unpack phase to
substitute the entire .cabal file?
Troy
[0] https://github.com/commercialhaskell/all-cabal-files
[1] https://github.com/commercialhaskell/all-cabal-files/blob/hackage/old-time/1.1.0.3/old-time.cabal#L3
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEE0zLJ6STd4Cp+CgbIgs677ofYV8IFAlikrIsACgkQgs677ofY
V8JDow//VxkiaNLTaZm72oK3d3/YZ+QbXmLlnC4NT1x2YFccMperaiR3JMjlotFD
1t9QWzppy2URRjJ8UcsbcuuVH5OVMpJZ8t4iybpJRlu3eqg/2W89rD/b6FtCIIkT
0ot78TL/HoLlzyY2gkW0/zHIAcMuEYNZvPmdUMteneqF6K8GuViMedxgMZ0TuMRT
QTkR6R7lOfNcYf670BU+giFsKMC1q+zqfEHtu16d+M3p970q6PjcwUFO1XdGoeZ8
BrSsBK5lYIFUBHBT85gZFePAi2hUchb2sPAg8peMkWkFiQbUi+C8yy92iWUUcgT2
lLhkAncty0VV4zToQtyTA+j1nKa/CnzYHSkV/n+hTA/yRXqsR1GZqa7dxnANAPQ6
M406A5K/Ntr6d0cbXRvBjbR0Bpr1kKSDQ5Y8fIsLHFnSk9pPXNqKamF4yBH/ROy5
aj/YOMVZ/PxUR57P4bbR8Ciaxx9KPvJS8UwO5RjszvSEzh+NLYKvC6Xa2OAHq8xs
cFHs71vG3giHpeX9rm4nRPcDyitfCEISOXtZPEQ6hc8RYVur/aqBd1wTgjAG8BXQ
0Alq9dbjnkvfouXZkheWRxx/r4NJx5ypImQ0RAoGpnrKFFGR/LVNckSZgXMQQykR
uMEyFm3AcuejO02yE94UXhqxXauSZwhnyFGe85NezHxZBnsD7ss=
=BsnY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-02-15 19:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 8:03 updating many haskell packages 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2017-02-06 5:23 Troy Sankey
2017-02-06 15:47 ` Leo Famulari
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=148718709098.32672.6688568200387118544@what \
--to=sankeytms@gmail.com \
--cc=beffa@ieee.org \
--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).