public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nick Rout <nick@rout.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Pratical question about portage tree
Date: Wed, 28 Sep 2005 16:41:58 +1200	[thread overview]
Message-ID: <20050928163705.53E7.NICK@rout.co.nz> (raw)
In-Reply-To: <200509280108.53868.nbensa@gmx.net>


On Wed, 28 Sep 2005 01:08:53 -0300
Norberto Bensa wrote:

> Dave Nebinger wrote:
> > Unfortunately Allen I don't remember exactly what the script was or
> > where I got it, but I think there's a reference to it in the Gentoo
> > Wiki.
> 
> It is not that hard actually:
> 
> comm -13 <(ls /usr/portage/distfiles | sort | uniq) \
>     <(for i in $(emerge -pufv world 2>&1 | grep ^http | awk '{ print $1 }')
>         do
> 	    echo $(basename $i)
>         done | sort | uniq)
> 
> That will print the files you'll need to download. Note however that it will 
> only print the filenames. You'll have to add:
> 
>     http://distfiles.gentoo.org/distfiles/ 
> 
> and perhaps -in some cases- other sources/servers as not everything is in 
> d.g.o
> 
> Regards


portage knows where to download the files from, and you have told it
where the best mirrors are for you, why second guess it!

How about 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.

-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-09-28  4:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28  1:05 [gentoo-user] Pratical question about portage tree Allan Spagnol Comar
2005-09-28  1:13 ` Nick Rout
2005-09-28  2:52 ` Dave Nebinger
2005-09-28  4:08   ` Norberto Bensa
2005-09-28  4:41     ` Nick Rout [this message]
2005-09-28 11:03       ` Allan Spagnol Comar
2005-09-28 11:58       ` Norberto Bensa
2005-09-28 21:24         ` Nick Rout
2005-09-28 23:22           ` Norberto Bensa
2005-09-29  0:57             ` W.Kenworthy
2005-09-29  1:27               ` Nick Rout
2005-09-29  2:22                 ` W.Kenworthy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050928163705.53E7.NICK@rout.co.nz \
    --to=nick@rout.co.nz \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox