Summary: | Devmanual should clarify about system packages deps | ||
---|---|---|---|
Product: | Documentation | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | Devmanual | Assignee: | Gentoo Quality Assurance Team <qa> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Other | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Diego Elio Pettenò (RETIRED)
2006-10-17 16:10:13 UTC
Care to suggest a patch against /var/svnroot/devmanual/trunk I don't see a documentation issue here. The same problem you listed here could happen if I had a broken gcc, glibc, tar, gzip, binutils, etc. Please reopen if you can make the issue with devmanual clearer. QA team has to decide on _exactly_ what the practise should be in regard to system packages, and make that well cleared. QA team didn't address this in fourteen months, it's not just a issue with the devmanual per se, but it's still well an issue. It's quite simple. Only specify system things as deps if you have a good reason for doing so. (In reply to comment #3) > QA team has to decide on _exactly_ what the practise should be in regard to > system packages, and make that well cleared. Which part of this is not clear? http://devmanual.gentoo.org/general-concepts/dependencies/index.html#implicit-system-dependency The problem you listed here is a problem with the dependency resolver if anything. System packages should not be listed unless there is a very very good reason. Just because you had a broken zlib package doesn't mean that the documentation or QA's policies are wrong. The same exact issue could come up when your gcc is completely busted. How are we supposed to address that situation? And again, we go back to closed, as the documentation is pretty clear for when you should add system packages into dependencies (unless you can point out how it isn't) Thanks |