Alec Warner wrote:
> Mike Frysinger wrote:
>> On Thursday 04 January 2007 20:33, Gustavo Felisberto wrote:
>>> Ok, so what is diference?
>> probably the samething as between -k and -K
>> -mike
> 
> A more verbose answer:
> 
> -k says "use binary packages if possible, otherwise use ebuilds"
> -K says "use only binary packages, fail if you can't create a depgraph"
> 
> -g says "use remote binary packages if possible, otherwise use ebuilds"
> -G says "only use remove binary packages, fail if you can't create a
> depgraph"
> 
> 
> I'd have to double check -g to make sure ebuilds are the fallback; you
> may be able to do something like
> 
> emerge -g -k
> 
> but in this case I'm pretty sure the remote binrepo will 'shadow' the
> local one, I'd have to ask Zac to be sure ;)
My main issue is with size. Right now portage has to pull ALL the packages in
the PORTAGE_BINHOST to create the dep tree. Is there a way for me to say:

emerge -u --use-bynary-packages-if-possible system and portage will build the
dep tree based on the local portage tree, then it will try to fetch the updated
packages and see if the deps are ok.

-- 
Gustavo Felisberto
(HumpBack)
Web: http://dev.gentoo.org/~humpback
Blog: http://blog.felisberto.net/
------------
It's most certainly GNU/Linux, not Linux. Read more at
http://www.gnu.org/gnu/why-gnu-linux.html .
-------------