public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Haskell packages and keeptemp
Date: Mon, 21 Sep 2015 00:29:38 -0400	[thread overview]
Message-ID: <55FF87B2.6030401@gentoo.org> (raw)
In-Reply-To: <20150920205820.19c3bb32@khumba.net>

On 09/20/2015 11:58 PM, Bryan Gardiner wrote:
> Hi gentoo-users,
> 
> I thought I would set FEATURES=keeptemp in make.conf so I would have
> build logs around for reference.  This causes problems with Haskell
> packages, which fail during the second build after setting this,
> because the build's temp/ hasn't been cleaned from the previous build:
> 
> ...
> 
> Am I wrong in expecting ${T} to be wiped at the start of a build,
> regardless of the package, so that this isn't a problem?  I'm not sure
> why you'd want old temp/ state to carry forward to the next build.
> 

Please open a bug. Portage probably has its own reasons for handling
${T} the way it does.

The problem with the Haskell stuff is (in haskell-cabal.eclass),

  # Newer cabal can generate a package conf for us:
  ./setup register --gen-pkg-config="${T}/${P}.conf"
  ghc-install-pkg "${T}/${P}.conf"

and the cabal routine doesn't want to overwrite an existing file. I'm
sure this is easy to fix with an "rm -f" beforehand.

But, maybe the reason portage doesn't wipe the directory is because
portage doesn't wipe the directory. If doing so would be an improvement,
they might choose to fix it there instead.



  reply	other threads:[~2015-09-21  4:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21  3:58 [gentoo-user] Haskell packages and keeptemp Bryan Gardiner
2015-09-21  4:29 ` Michael Orlitzky [this message]
2015-09-21  5:03   ` Bryan Gardiner
2015-09-21  5:29 ` J. Roeleveld
2015-09-21  6:41   ` Bryan Gardiner
2015-09-21  6:55     ` Alan McKinnon
2015-09-21 15:37       ` Bryan Gardiner

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=55FF87B2.6030401@gentoo.org \
    --to=mjo@gentoo.org \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox