public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] PORTAGE_BINHOST Madness
Date: Sat, 06 Jan 2007 03:15:53 -0500	[thread overview]
Message-ID: <459F5AB9.3090002@gentoo.org> (raw)
In-Reply-To: <459F06D1.5070601@gentoo.org>

Gustavo Felisberto wrote:
> 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.
> 

meh..You want to build a depgraph on local ebuilds, and then try to find
matching binpkgs after the fact?  I'd imagine you'd have a lot of
trouble finding matching packages, tbh :)

Ebuilds in the tree will get updated, or your local USE flags will
change; your binary packages won't match in either case here, because
the tree has a more up to date package or a package with correct flags.
 Thats why the binary repo is used for the deptree generation.

Talk to solar about binhost, I know he has a better implementation lying
around; it's a matter of finalizing it ;)
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-01-06  8:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05  1:33 [gentoo-dev] PORTAGE_BINHOST Madness Gustavo Felisberto
2007-01-05  1:54 ` Mike Frysinger
2007-01-05  5:15   ` Alec Warner
2007-01-06  2:17     ` Gustavo Felisberto
2007-01-06  8:15       ` Alec Warner [this message]
2007-01-07  5:16         ` [gentoo-dev] " Steve Long
2007-01-08 20:14           ` Ned Ludd
2007-01-09  0:15             ` [gentoo-dev] " Steve Long

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=459F5AB9.3090002@gentoo.org \
    --to=antarus@gentoo.org \
    --cc=gentoo-dev@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