On Sun, 18 Mar 2012 14:18:22 -0700 Mark Knecht <[email protected]> wrote:
> Hi, > I have a system in which I've never used the buildpkg feature so I > have no packages. The machine is completely up to date - i.e. - emerge > -DuN @world does nothing new. > > I know if I turn on buildpkg and do an emerge -e @world, assuming > all the compiling completes without error, emerge will create packages > for everything that's install. That however takes lots of time. > > I was reading about the quickpkg feature which supposedly creates > packages from what's already installed, but I'm not sure how to > actually run that for a complete system like this. If I put > FEATURES="quickpkg" in make.conf and run emerge -e @world, will emerge > simply make the packages for anything that's already installed, but > not actually compile the packages themselves? > > Thanks, > Mark > RTFM :-) "man quickpkg" lists "quickpkg @system" in the examples section. "quickpkg @world" works and does what you expect - tar and gzips the entire package as it is on-disk. As to what is in the quickpkg, it's the same list as you get from "equery files <pkg_name>. Thereafter, enable FEATURES="quickpkg" and portage will keep everything new up to date. Also read up on eclean, which helps to remove old quickpkg cruft -- Alan McKinnnon [email protected]
