I _can_, of course, whip up a web/ftp server to host “local” files, but I shouldn’t have to.. I’d also love to see the list of supported schemes *documented* in ebuild(5)... I thought “file://“ scheme would “just work”, but no dice: —-- # ebuild nxclient-3.5.0.7.ebuild digest >>> Downloading 'file:///etc/portage/overlay/distfiles/nxclient-3.5.0.7.x86_64.tar.gz' file:///etc/portage/overlay/distfiles/nxclient-3.5.0.7.x86_64.tar.gz: Unsupported scheme 'file'. !!! Couldn't download 'nxclient-3.5.0.7.x86_64.tar.gz'. Aborting. !!! Fetch failed for nxclient-3.5.0.7.x86_64.tar.gz, can't update Manifest --- No luck with “tftp://“ either: —-- # ebuild nxclient-3.5.0.7.ebuild digest >>> Downloading 'tftp://pkg:/gentoo/nxclient-3.5.0.7.x86_64.tar.gz' tftp://pkg:/gentoo/nxclient-3.5.0.7.x86_64.tar.gz: Unsupported scheme 'tftp'. !!! Couldn't download 'nxclient-3.5.0.7.x86_64.tar.gz'. Aborting. !!! Fetch failed for nxclient-3.5.0.7.x86_64.tar.gz, can't update Manifest --- After some reading, I did find a workaround (only relevant parts shown): +++ SRC_URI=“${FULL_PACKAGE_FILE_NAME}" RESTRICT=“fetch" pkg_nofetch() { cp -vu ${FILESDIR}/${SRC_URI} /usr/portage/distfiles } +++ Still, I think support for “file://“ (and other schemes) would be a lot more natural..
*** This bug has been marked as a duplicate of bug 334275 ***
