Seriously this time:
How about changing your strategy to this:
Get a list of the packages you want to update from the target machine.
something like:
emerge -uDp world|grep ebuild|awk '{print($4)}'>packlist
take packlist to the connected machine and type:
for package in `cat packlist` ; do DISTDIR=/where/ever/i/want emerge
--nodeps -f =$package; done
The files will then be in /where/ever/i/want and you can put them on a
cd or whatever method you are using and take them away.
--nodeps will make sure that your connected host doesn't substitute its
own idea of what the deps are (perhaps based on different USE flags)
You could also probably do something like:
for package in `cat packlist` ; do DISTDIR="/where/ever/i/want"
GENTOO_MIRRORS="local
/usr/portage/distfiles" emerge --nodeps -f =$package; done
The GENTOO_MIRRORS="local /usr/portage/distfiles" should take files from
the local system in preference to downloading them, which will save your
bandwidth, although i am not 100% sure of the syntax.
In other words let your network connected host choose where to download
from.
On Fri, 19 Aug 2005 08:18:08 -0700
Grant wrote:
> Hello, a little while ago I asked this list for help with updating a
> machine with no network connection. The solution was to get a txt
> list of the package paths and then download them on a networked
> machine with this command:
>
> sort -u links.txt | xargs -n 1 -i{} sh -c 'for i in {}; do wget -c $i
> && break; done'
>
> This worked great then, but something must have changed because that
> now only downloads about 12 or so files and then quits without an
> error. There are a lot more packages in links.txt to be downloaded.
> Does anyone know how to fix this?
>
> - Grant
>
> --
> gentoo-user@gentoo.org mailing list
--
Nick Rout <[EMAIL PROTECTED]>
--
gentoo-user@gentoo.org mailing list
