Summary: | emerge --depclean improvement | ||
---|---|---|---|
Product: | Portage Development | Reporter: | David Carlos Manuelda <StormByte> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
David Carlos Manuelda
2006-07-20 18:29:55 UTC
The dependency data is already stored in /var/db/pkg/*/*/*DEPEND. Is this a duplicate of bug 41417 ? I didn't want to say the dependency data /var/db/pkg/*/*/*DEPEND BEFORE compiling, I was saying to store that dependency data AFTER merging software, and that way, when certain time has passed (merging and unmerging some apps) you will know accurately *why* all the packages were installed and *what* program required it. It is completely different to storing DEPEND data in an ebuild to has all its dependencies ready in compile time. Maybe I explained it wrong. Is it clear now what I wanted to say? I don't understand what you're trying to say. "It is completely different to storing DEPEND data in an ebuild to has all its dependencies ready in compile time." <- doesn't make any sense to me. I was trying to say that DEPEND stores the dependency tree for compiling purposes (avoiding compilations fails, enable/disable features, etc..). But what I was trying to expose is to keep track of all packets, and *WHY* were them installed (what application(s) required it). This way, you can now why were installed certain packets before attempting to remove them. For example, with libqt(32 bits emulated)(I forgot name of ebuild): much apps require it, but system changes as time goes by, so I can easyly forget what app requested this libs, it would be unsafe to simply remove from system, 'cause there could be some apps wich are still using it. With this idea, this can be avoided 'cause the record of wich package makes install of another (as dependency) is keps for all packages. Is it More clear now? (sorry, I cannot explain better in english :) ) I still don't see the difference between storing RDEPEND="foo" in bars vdb entry and storing "package foo requested by bar" in your suggested system. The info is the same, you just seem to express it differently. If you can give me an *actual* example where the dep info that's currently stored in vdb is inadequate. |