On Sun, Apr 13, 2003 at 03:47:06AM -0400, Jon Portnoy wrote:
> 
> Capital K, which (I believe) is use binary packages only.
> 

Yes, you are correct. Please take note, the man page is out-of-date.

With capital K I belive I have what I need ;)

Thanks Jon!

Best regards
 Michael Boman

> On Sun, Apr 13, 2003 at 03:45:21PM +0800, Michael Boman wrote:
> > On Sun, Apr 13, 2003 at 03:40:02AM -0400, Jon Portnoy wrote:
> > > 
> > > I think the -K option for emerge does this.
> > > 
> > > On Sun, Apr 13, 2003 at 03:36:21PM +0800, Michael Boman wrote:
> > > > Is there a way to let machines only see (updated) pre-compiled packages
> > > > when they do 'emerge -p world'? I am thinking of providing a local
> > > > repository of "authorized/tested" software over NFS and when you do
> > > > 'emerge world' it will take the latest version from the pre-compiled
> > > > pile of packages, totally ignoring what is availble as ebuild's from
> > > > rsync.gentoo.org or in the PORTAGE_OVERLAY dir..
> > > > 
> > > > Doable? How?
> > 
> > From the emerge man-page:
> > 
> >    --usepkg (-k)
> >           Tells  emerge  to use binary packages (from $PKGDIR) if they are
> >           available, thus possibly avoiding some time-consuming  compiles.
> >           This   option   is  useful  for  CD  installs;  you  can  export
> >           PKGDIR=/mnt/cdrom/packages and then  use  this  option  to  have
> >           emerge  "pull"  binary  packages from the CD in order to satisfy
> >           dependencies.
> > 
> > My biggest problem is the wording
> >  "to use binary packages (from $PKGDIR) >>if<< they are available"
> > 
> > It hints that if a newer ebuild is availble it will still be compiled,
> > and not taken from the pre-compiled repository.
> > 
> > If I am wrong please let me know ;)
> > 

-- 
Michael Boman
Security Architect, SecureCiRT Pte Ltd
http://www.securecirt.com