Summary: | Separate libstdc++ out of gcc package | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Carlos Manuelda <StormByte> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | zmedico |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
David Carlos Manuelda
2015-07-24 20:03:16 UTC
Not really. Maybe you could just remove the binaries. (In reply to Ryan Hill from comment #1) > Not really. Maybe you could just remove the binaries. It may be possible in the future, using portage, to identify libraries that we need to leave behind when unmerging a package. I'm cc-ing zmedico because he has been working on consumer/provide code in portage to track this sort of information in the linkage map. Maybe an option in portage like --safe-unmerge which is not a sledgehammer like --unmerge, but also not as restrictive as --depclean. --safe-unmerge = "remove the package and don't worry about dependencies, but leave behind any files that other packages report as needed for consumption, and don't orphan these extra files either, but keep track of them in case I want to clean them up later." I do see merit in the reporter's request. In the past, when I've mastered things like amazonaws images, I've just followed Ryan's approach and deleted binaries which hand baked scripts. But having this in portage might be nice. @zmedico. This might be something that easily comes out of what you've been doing without much extra work. What do you think? (Thinking out loud.) |