Archives
Archives
| From: | Nikos Chantziaras <realnc@×××××.com> | ||
|---|---|---|---|
| To: | gentoo-user@l.g.o | ||
| Subject: | [gentoo-user] Re: How to trace down compilation issues if the compilation does not break...? | ||
| Date: | Mon, 07 Jan 2019 04:37:27 | ||
| Message-Id: | q0ukth$td6$1@blaine.gmane.org | ||
| In Reply to: | [gentoo-user] How to trace down compilation issues if the compilation does not break...? by tuxic@posteo.de | ||
| 1 | On 06/01/2019 17:31, tuxic@××××××.de wrote: |
| 2 | > The problem with this problem is, that the compilation process |
| 3 | > is successful and all files will be removed from /var/tmp/portage |
| 4 | > afterwards. |
| 5 | > |
| 6 | > I checked the manpage of emerge to find an option to prevent the |
| 7 | > deletion of the remainders, but found nothing. |
| 8 | |
| 9 | You can set FEATURES=keeptemp while emerging the package for which you |
| 10 | want to keep the tmp files. In your case: |
| 11 | |
| 12 | sudo FEATURES=keeptemp emerge -1 media-gfx/krita |
| Subject | Author |
|---|---|
| Re: [gentoo-user] Re: How to trace down compilation issues if the compilation does not break...? | tuxic@××××××.de |