Summary: | x11-wm/compiz abusing ${ROOT} | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thilo Bangert (RETIRED) (RETIRED) <bangert> |
Component: | New packages | Assignee: | Desktop-Effects herd <desktop-effects+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 258096 |
Description
Thilo Bangert (RETIRED) (RETIRED)
2009-02-08 12:50:59 UTC
The only use of ${ROOT} in compiz is for the following: ln -s "${ROOT}"/usr/share/aclocal/gconf-2.m4 acinclude.m4 The only reason this is being done is because the acinclude.m4 in compiz was causing issues. As we're linking to a macro file, how are we abusing ${ROOT}? ROOT is used to influence where stuff is being installed (into a different root), but has no relation to where stuff is, when the package is being built. all build time dependencies have to be (and are) met by whatever is installed in /. in the case of x11-wm/compiz, you would simply remove the ROOT variable. you would for example use the ROOT variable, if you want to warn the user of an old and obsoleted config file, which you find to be present (in pkg_postinst()). Thilo, thanks for the explanation. I've removed ${ROOT} from the ebuild. I've fixed this on compiz-0.8.2 that I just added to the tree. |