| 1 |
On 09/20/2015 11:58 PM, Bryan Gardiner wrote: |
| 2 |
> Hi gentoo-users, |
| 3 |
> |
| 4 |
> I thought I would set FEATURES=keeptemp in make.conf so I would have |
| 5 |
> build logs around for reference. This causes problems with Haskell |
| 6 |
> packages, which fail during the second build after setting this, |
| 7 |
> because the build's temp/ hasn't been cleaned from the previous build: |
| 8 |
> |
| 9 |
> ... |
| 10 |
> |
| 11 |
> Am I wrong in expecting ${T} to be wiped at the start of a build, |
| 12 |
> regardless of the package, so that this isn't a problem? I'm not sure |
| 13 |
> why you'd want old temp/ state to carry forward to the next build. |
| 14 |
> |
| 15 |
|
| 16 |
Please open a bug. Portage probably has its own reasons for handling |
| 17 |
${T} the way it does. |
| 18 |
|
| 19 |
The problem with the Haskell stuff is (in haskell-cabal.eclass), |
| 20 |
|
| 21 |
# Newer cabal can generate a package conf for us: |
| 22 |
./setup register --gen-pkg-config="${T}/${P}.conf" |
| 23 |
ghc-install-pkg "${T}/${P}.conf" |
| 24 |
|
| 25 |
and the cabal routine doesn't want to overwrite an existing file. I'm |
| 26 |
sure this is easy to fix with an "rm -f" beforehand. |
| 27 |
|
| 28 |
But, maybe the reason portage doesn't wipe the directory is because |
| 29 |
portage doesn't wipe the directory. If doing so would be an improvement, |
| 30 |
they might choose to fix it there instead. |
Archives