If a package lives in ${PORTAGE_OVERLAY}, then the ebuild command "unpack( <archive> )" should look for tarballs in ${PORTAGE_OVERLAY}/${CATEGORY}/${PF}/files/, rather than ${PORTAGE}/${CATEGORY}/${PF}/files/, which is where it looks now. In fact, it entirely ignores the overlay directory, and there is no logical reason for it to base the search for supplemental files in the regular Portage home directory when the ebuild itself lives in the overlay directory. If there /is/ a way to get unpack to look in the overlay directory, then this should be a bug report about unpack being poorly documented ;-) To see this bug in action, pull the Karamba [http://www.kdelook.org/content/show.php?content=5649] ebuild package, place it in the overlay directory, and attempt to install it.
Why? It's a waste of space to do that...
How do you mean, a waste of space? $PORTAGE_OVERLAY is the sanctioned place to put packages that aren't in rsync.
I think you should look at that now, seems to be fixed but I'm not sure... :-) Radek
${FILESDIR} is set correctly, don't know if it was ever wrong. Tarballs are still in ${DISTFILES} ignoring where the ebuild lives.
