>>>>> On Mon, 15 Oct 2018, Michael Haubenwallner wrote:

> in pkg_nofetch, beyond to "direct the user to download relevant
> source files", I've found it useful to tell the user which
> filesystem directory to put the files into once downloaded.

> Beyond that, I've also found it useful to tell the user whether a
> relevant source file is 'already there' or 'still missing'.

> Since the EAPI 6 related update to pkg_* phases to not have access
> to DISTDIR (even in earlier EAPI) any more, I'm wondering if both
> informations are still available to pkg_nofetch in one or another
> way.

DISTDIR was never officially available in any of the pkg_* phases.
(This was the case both in EAPI 0, and in PMS as early as 2008.)

Then again, even in the src_* phases the variable will point to a
temporary shadow directory in recent Portage version, not to the real
directory containing the distfiles.

> Any idea?

> Or is my only option to reduce the information to "all these files
> need to be put in your DISTDIR", requiring the user to find out both
> the right DISTDIR and which of the listed files are still missing
> herself?

I think there is no good way to tell them more than that. Even if
DISTDIR was available in pkg_* scope, users may prefer to drop
manually downloaded files into PORTAGE_RO_DISTDIRS, which is a Portage
specific location.

Ulrich