| 1 |
On 03/28/2015 01:17 PM, James wrote: |
| 2 |
> |
| 3 |
> Is there a way to includes those files for archiving so something like |
| 4 |
> elogviewer could make them available systematically? Do you think the |
| 5 |
> maintainer of elogviewer is open to that sort of request, formally (BGO) or |
| 6 |
> informally (personal email?). Another more suited tool for extending the |
| 7 |
> existing functionality to view key files of an ebuild? |
| 8 |
|
| 9 |
FEATURES="noclean" will leave the entire built source tree intact. It |
| 10 |
will waste a bunch of space but you'll have a copy of the files you want. |
| 11 |
|
| 12 |
The package manager is what normally deletes those files, so if you |
| 13 |
wanted to file a feature request somewhere, it would have to be with |
| 14 |
portage. IMO I think they'll say no, but you could request something |
| 15 |
like a CLEAN_MASK variable that allows you to prevent certain files from |
| 16 |
being cleaned. |
Archives