From: Timothy Sample <samplet@ngyro.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: merge wip-haskell?
Date: Sun, 09 Aug 2020 00:29:35 -0400 [thread overview]
Message-ID: <87a6z4qw5s.fsf@ngyro.com> (raw)
In-Reply-To: 87r1si5j23.fsf@elephly.net
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> writes:
> Timothy Sample <samplet@ngyro.com> writes:
>
>> Also, it looks like “wip-haskell-updates” is no longer being built by
>> the CI infrastructure. Since the branch triggers a rebuild of all the
>> Haskell packages, it should be built before merging, right?
>
> Yes, I’ll rebase it on top of “master” and add the specification to
> ci.guix.gnu.org well before the merge.
Excellent.
I just pushed “wip-haskell-updates-2” which integrates my work from
<https://issues.guix.gnu.org/39309>. I left the original branch intact
to make it easy to compare.
Basically, where you remove the “--extra-include-dirs” and
“--extra-lib-dirs” arguments in configure, I preserve them and hide them
behind a build system argument. To do this, I split up the commit where
you remove them into a refactor commit (where you remove “append” and
just use quasiquoting), and a commit that removes “--bindir”. My commit
goes in the middle.
Then, I remove the commits that fix up ghc-hslua, ghc-libyaml, and
ghc-zlib, as that’s handled in my commit.
The only other thing I did was move the shared libraries commit sooner,
since it needs to be in place for the static output commit to work (at
least nothing would build for me without it).
With respect to the substance of your changes, I think the results are
worth the ugliness! Keeping “ghc-pandoc” as the “normal” package and
using “pandoc” for the statically linked one makes sense if feasible.
Unfortunately, I don’t know of a better way to get all the static
libraries in place.
It would be nice if there was a way to get similar improvements without
static linking, but I imagine it would be tough. I’m not suggesting
anything for now, but maybe we could split the GHC package so that other
packages could reference the “base” library (125M) without referencing
the “ghc” and “Cabal” libraries (818M). Ultimately it would be nice to
have a more general solution.
In the meantime, I think that this is fine.
-- Tim
next prev parent reply other threads:[~2020-08-09 4:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 8:13 merge wip-haskell? Ricardo Wurmus
2020-08-06 13:45 ` John Soo
2020-08-07 17:46 ` Timothy Sample
2020-08-07 19:53 ` Ricardo Wurmus
2020-08-09 4:29 ` Timothy Sample [this message]
2020-08-12 12:21 ` Ricardo Wurmus
2020-08-13 15:37 ` Ricardo Wurmus
2020-08-15 8:19 ` Ricardo Wurmus
2020-08-17 15:22 ` Timothy Sample
2020-08-24 15:38 ` Ludovic Courtès
2020-08-07 15:03 ` Jakub Kądziołka
2020-08-07 15:12 ` John Soo
2020-08-07 15:46 ` Jakub Kądziołka
2020-08-07 15:59 ` Ricardo Wurmus
2020-08-07 16:08 ` John Soo
2020-08-24 15:44 ` Ludovic Courtès
2020-08-24 17:54 ` Ricardo Wurmus
2020-08-28 13:53 ` Ludovic Courtès
2020-08-28 14:05 ` John Soo
2020-08-28 17:29 ` Timothy Sample
2020-08-29 15:34 ` Timothy Sample
2020-08-29 15:54 ` John Soo
2020-08-07 16:27 ` Ricardo Wurmus
2020-08-07 16:55 ` Jakub Kądziołka
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=87a6z4qw5s.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.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).