Yo. Shouldn't be an issue unless you're doing something crazy, but the DISTDIR var exported to ebuilds will now point to an intermediate directory; all files stated via SRC_URI will be symlinks pointing back to the actual file in DISTDIR.
Why? Well prior to this modification, it was possible for ebuild devs to overlook unstated SRC_URI files. Eg, direct access to DISTDIR, even if the file wasn't stated in SRC_URI, they still could use it. They also could commit it, where it would break for anyone who used it. Happens on occasion. Other angle is that RESTRICT="fetch", due to the fact portage isn't fetching, it was possible for the file to be left out of SRC_URI (thus no digest info). With this mod, if it's not stated in SRC_URI, it's not accessible. Basically, if your ebuild is broke, it *will* break now rather then working locally for you. Downside is that since certain class of ebuilds don't state their files in SRC_URI (namely subversion and cvs based ebuilds), they're broken by the change. So... PORTAGE_ACTUAL_DISTDIR is added (eclasses modified already for it), that holds the actual DISTDIR location. Don't use PORTAGE_ACTUAL_DISTDIR unless you have to. Four cases where it's valid in the tree, shouldn't be anymore. That var *will* go away when/if cvs/svn support is via SRC_URI. Meanwhile, notifying y'all so any further complaining/issues are stated before this goes stable. Bug in question is 117440 http://bugs.gentoo.org/117440 Questions, either comment here or track me down in irc. ~harring
pgpQMSRBLRYeM.pgp
Description: PGP signature
