Summary: | packages that fail in src_compile/pkg_setup stage because their additional checks fail | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Robin Johnson <robbat2> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | greg_g |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robin Johnson
2005-03-11 22:59:35 UTC
I fail to see the actual point of this bug ... Most of these problems aren't related other than PHP being involved and at least 4) and 5) (and likely 2) already have their own bugs. The other two are clearly package bugs from my POV. genone: ferringb asked me to document my discussion I had with him, as to things that can break a build, and we can't check for at dependancy calculation time presently. 1. could be consider a bug, but how else can we easily provide certain sets of functionality for users, dealing with packages that aren't in the tree at all (Oracle esp.). We just let them install it manually, and then set the related USE flag - but this breaks RDEPENDs. The notion of packages that purposefully fail doesn't break RDEPEND, but it does break an automated build if the packages get pulled in. 2. just depending on virtual/jdk doesn't gaurentee a compatible JDK is set with java-config, which is why we need a check in the ebuild, and then this causes a build to fail if things aren't right. 3. again, this is a case where the ebuild has to check the current system, to see if it can compile properly, and fail if not, this breaks automated builds again, but I don't see any way to work around it. #4 and #5 i'll leave since you say bugs already exist for those items. Another one now, in net-nds/openldap-2.2.23-r1. If you try upgrade from openldap-2.1 to 2.2, without following the upgrade instructions, then it WILL corrupt your database. To work around this, pkg_setup detects if you are doing an upgrade from 2.1 to 2.2, and displays the upgrade instructions, then fails out. Again, if this happens N hours into a build process, it stops the automated build. 5 doesn't belong here. *** This bug has been marked as a duplicate of 75936 *** |