all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: John Soo <jsoo1@asu.edu>
Cc: 38593@debbugs.gnu.org
Subject: [bug#38593] Remove invalid library directories from some haskell packages
Date: Thu, 19 Dec 2019 23:30:20 +0100	[thread overview]
Message-ID: <871rt0kkxv.fsf@gnu.org> (raw)
In-Reply-To: <CAKf5CqXw-e+Rc2ytbcEZhai2kv18YQutK1pr7un5P6UgpZ74kQ@mail.gmail.com> (John Soo's message of "Fri, 13 Dec 2019 14:38:01 +0000")

Hi,

John Soo <jsoo1@asu.edu> skribis:

> When compiling with ghc, I have been getting the message that the following
> packages have invalid package databases.

Does it hurt in practice, or are these invalid databases shadowed by the
one created in the profile?

> diff --git a/gnu/packages/haskell-xyz.scm b/gnu/packages/haskell-xyz.scm
> index fb6833207d..1d78eb7894 100644
> --- a/gnu/packages/haskell-xyz.scm
> +++ b/gnu/packages/haskell-xyz.scm
> @@ -5500,6 +5500,13 @@ representations of current time.")
>         ("ghc-quickcheck" ,ghc-quickcheck)
>         ("ghc-temporary" ,ghc-temporary)
>         ("hspec-discover" ,hspec-discover)))
> +    (arguments
> +     `(#:phases
> +       (modify-phases %standard-phases
> +         (add-after 'install 'remove-lib
> +           (lambda* (#:key outputs #:allow-other-keys)
> +             (delete-file-recursively
> +              (string-append (assoc-ref outputs "out") "/lib")))))))

Should we add a phase in ‘haskell-build-system’ that systematically
removes package databases?

Thanks,
Ludo’.

  parent reply	other threads:[~2019-12-19 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 14:38 [bug#38593] Remove invalid library directories from some haskell packages John Soo
2019-12-18 12:41 ` [bug#38593] [PATCH] " John Soo
2019-12-19 22:30 ` Ludovic Courtès [this message]
2019-12-20 21:28   ` [bug#38593] " John Soo
2019-12-20 21:28     ` John Soo
2021-01-01 18:30 ` bug#38593: Have not experienced this problem in a long time John Soo

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

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

  git send-email \
    --in-reply-to=871rt0kkxv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=38593@debbugs.gnu.org \
    --cc=jsoo1@asu.edu \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.