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: Thu, 29 Sep 2005 09:24:46 +1200	[thread overview]
Message-ID: <20050929090918.53F4.NICK@rout.co.nz> (raw)
In-Reply-To: <200509280858.53079.nbensa@gmx.net>


On Wed, 28 Sep 2005 08:58:52 -0300
Norberto Bensa wrote:

> Nick Rout wrote:
> >
> > portage knows where to download the files from, and you have told it
> > where the best mirrors are for you, why second guess it!
> 
> What I've made is download _only_ needed files. For this to work, I've had to 
> remove path names (i.e. http://download.from.server.tld/path/to/filename.tgz 
> becomes filename.tgz) 
> 
> >
> > for package in `cat packlist` ; do DISTDIR=/where/ever/i/want emerge
> > --nodeps -f =$package; done
> 
> This assumes _both_ machines have Gentoo _and_ exactly the same USE flags.
> 
> >
> > --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)
> 
> In most cases, you will end with partially downloaded packages.
> 
> 

No it won't, why do you say that (although please read below because I
realise that there is an error with my strtegy because of the possible
difference in USE flags)

> > In other words let your network connected host choose where to download
> > from.
> 
> My method, although not the best, works under Windows and other OSes too ;-) 

That was not the question posed. The question assumed:

Machine A with updated portage and all updates emerged.
Machine B with poor network access, and its portage updated from Machine A

So both machines will have the same portage, but admittedly may not have
the same USE flags.

I think you are right in saying that the USE flag differences will cause problems with my method. This is because:

1. Different USE flags may result in different dependencies for a given
package; and

2. Different USE flags may result in different download files even
within the same package.

OTOH your approach has problems in that not all files reside on gentoo
mirrors, some reside on sourceforge or other more obscure places.

IMHO my approach can be fixed by:

1. On machine B, as well as running:

emerge -uDp world|grep ebuild|awk '{print($4)}'>packlist

also run:

emerge info|grep USE |cut -d\" -f2 > B.uselist

2. On machine A, instead of running:

for package in `cat packlist` ; do DISTDIR="/where/ever/i/want" GENTOO_MIRRORS="local
/usr/portage/distfiles" emerge --nodeps -f =$package; done

run:

for package in `cat packlist` ; do DISTDIR="/where/ever/i/want" GENTOO_MIRRORS="local
/usr/portage/distfiles" USE="-* `cat B.uselist` emerge --nodeps -f
=$package; done


emerge will use the USE list from machine B, and will collect files
locally before grabbing them from the net.

Certainly, like most of linux, there is more than one way to do it. :-)






> 
> 
> >
> > --
> > Nick Rout <nick@rout.co.nz>
> 
> Best regards,
> Norberto
> 
> 
> -- 
> Norberto Bensa
> 4544-9692
> Ciudad de Buenos Aires, Argentina
> -- 
> gentoo-user@gentoo.org mailing list

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

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-09-28 21:29 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
2005-09-28 11:03       ` Allan Spagnol Comar
2005-09-28 11:58       ` Norberto Bensa
2005-09-28 21:24         ` Nick Rout [this message]
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=20050929090918.53F4.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