Having set DISTDIR to a custom path in 'make.conf' seems to have no effect: $ pkgdev --debug manifest /var/cache/distfiles/qt5compat-everywhere-src-6.3.2.tar.xz: No such file or directory * failed fetching files: dev-qt/qt5compat-6.9999::qt Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/pkgcore/operations/__init__.py", line 69, in _recast_exception_decorator return functor(*args, **kwds) File "/usr/lib/python3.9/site-packages/pkgcore/operations/format.py", line 137, in _cmd_api_fetch raise GenericBuildError('failed fetching required distfiles') pkgcore.operations.format.GenericBuildError: failed build operation: failed fetching required distfiles If I create the '/var/cache/distfiles' directory: /var/cache/distfiles/qt5compat-everywhere-src-6.3.2.tar.xz: Permission denied So the earlier error was probably more about the directory than the file, which seems to be eager to get under the default path.
It works fine for me. Could you share your make.conf?
Actually this seems to be about the location of 'make.conf'. Mine is still under the old path, '/etc/', and if I make another one under '/etc/portage' the custom path will be used. Not sure how supported such a configuration should still be, even if Portage and such work with it, since even the man page of Portage doesn't seem to mention the old location at all these days so ('man make.conf' does, however).
I really don't think we should support that legacy path. Portage had warned about it for years.
Yes, sorry pkgcore stack (pkgdev & pkgcheck included) aren't intended to support all legacy options of portage. This should be a clean and confirming configuration, which "/etc/make.conf" is very much far of. I may recommend to migrate to current accepted path, or symlink the files.
