On Sat, 19 Apr 2008 18:38:06 +0200
"Marijn Schouten (hkBst)" <[EMAIL PROTECTED]> wrote:
> Every package dependency in DEPEND is installed and usable before
> src_unpack starts, right? So is the question here whether or not they
> can be uninstalled right before pkg_{pre,post}inst starts?If we're using binaries, DEPEND is usually ignored. > I don't know what the general use of pkg_preinst is, but in > pkg_postinst the package itself should be runnable, so its RDEPENDS > should be installed and usable at this point. So perhaps we should > define that "usable" means "each of its RDEPENDs is installed and has > had its pkg_postinst function run". The recursion of that definition > then comes from the requirement that RDEPENDs should be usable before > pkg_postinst starts running. No good. That prevents RDEPEND <-> RDEPEND cycles from being solved, and the package manager has to be able to solve that. > If only one of those packages has a pkg_postinst then it is still > solvable. If they both have a pkg_postinst then one of those is > probably not essential for the actual usability of the package and > should be removed. A final possibility is that the pkg_postinsts are > both necessary for a fully functional package but not for the > functionality used in the other pkg_postinst. If this is the case, > then perhaps we should specify deps according to which ebuild phase > they are necessary for? Not with current EAPIs we can't. > SRC_UNPACK_DEP="app-arch/unzip" > SRC_COMPILE_DEP="dev-scheme/bigloo" > SRC_INSTALL_DEP="" Labels are a cleaner solution to this. But again, we're discussing current EAPIs here. -- Ciaran McCreesh
signature.asc
Description: PGP signature
