From: John Soo <jsoo1@asu.edu> To: "Ludovic Courtès" <ludo@gnu.org>, help-guix <help-guix@gnu.org> Cc: 38593@debbugs.gnu.org Subject: [bug#38593] Remove invalid library directories from some haskell packages Date: Fri, 20 Dec 2019 13:28:52 -0800 [thread overview] Message-ID: <69081139-A67A-43C5-8757-36437C6CC96D@asu.edu> (raw) In-Reply-To: <871rt0kkxv.fsf@gnu.org> Hi Ludo and guix, Let me explain my problem. Maybe there is some other explanation here and these patches aren’t necessary. When I have stylish-haskell installed I have troubles compiling anything using plain ghc. I want to use the ghc packages in the profile but for some reason ghc reports the database is invalid because of at least stylish-haskell and I think I’ve seen hoogle as well. > Does it hurt in practice, or are these invalid databases shadowed by the > one created in the profile? I’m not sure what you mean here. I think I dod not explained my problem well enough. Does the explanation above make sense? Another possibility is the duplication of path variables in tmux where I usually operate. Thinking now, maybe another explanation is because stylish-haskell and ghc-stylish-haskell are fighting each other? They are duplicate packages and maybe if one is removed it will be ok? > Should we add a phase in ‘haskell-build-system’ that systematically > removes package databases? I don’t think so. I like having the profile packages. A lot of times I prefer to use plain ghc with the profile packages over cabal or another tool so I’m happy to have the packages in the database. The ones I was considering removing were ones that primarily provide a binary to use - hoogle and stylish-haskell are primarily used as binaries. However on second thought if I wanted to use them as libraries I think I would be confused as to why I could not. Overall I am leaning towards finding some other solution. Thanks everyone! John
WARNING: multiple messages have this Message-ID (diff)
From: John Soo <jsoo1@asu.edu> To: "Ludovic Courtès" <ludo@gnu.org>, help-guix <help-guix@gnu.org> Cc: 38593@debbugs.gnu.org Subject: Re: [bug#38593] Remove invalid library directories from some haskell packages Date: Fri, 20 Dec 2019 13:28:52 -0800 [thread overview] Message-ID: <69081139-A67A-43C5-8757-36437C6CC96D@asu.edu> (raw) In-Reply-To: <871rt0kkxv.fsf@gnu.org> Hi Ludo and guix, Let me explain my problem. Maybe there is some other explanation here and these patches aren’t necessary. When I have stylish-haskell installed I have troubles compiling anything using plain ghc. I want to use the ghc packages in the profile but for some reason ghc reports the database is invalid because of at least stylish-haskell and I think I’ve seen hoogle as well. > Does it hurt in practice, or are these invalid databases shadowed by the > one created in the profile? I’m not sure what you mean here. I think I dod not explained my problem well enough. Does the explanation above make sense? Another possibility is the duplication of path variables in tmux where I usually operate. Thinking now, maybe another explanation is because stylish-haskell and ghc-stylish-haskell are fighting each other? They are duplicate packages and maybe if one is removed it will be ok? > Should we add a phase in ‘haskell-build-system’ that systematically > removes package databases? I don’t think so. I like having the profile packages. A lot of times I prefer to use plain ghc with the profile packages over cabal or another tool so I’m happy to have the packages in the database. The ones I was considering removing were ones that primarily provide a binary to use - hoogle and stylish-haskell are primarily used as binaries. However on second thought if I wanted to use them as libraries I think I would be confused as to why I could not. Overall I am leaning towards finding some other solution. Thanks everyone! John
next prev parent reply other threads:[~2019-12-20 21:30 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 ` [bug#38593] " Ludovic Courtès 2019-12-20 21:28 ` John Soo [this message] 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=69081139-A67A-43C5-8757-36437C6CC96D@asu.edu \ --to=jsoo1@asu.edu \ --cc=38593@debbugs.gnu.org \ --cc=help-guix@gnu.org \ --cc=ludo@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: linkBe 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.