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