1 |
On Sun, Mar 18, 2012 at 2:18 PM, Mark Knecht <markknecht@×××××.com> wrote: |
2 |
> Hi, |
3 |
> I have a system in which I've never used the buildpkg feature so I |
4 |
> have no packages. The machine is completely up to date - i.e. - emerge |
5 |
> -DuN @world does nothing new. |
6 |
> |
7 |
> I know if I turn on buildpkg and do an emerge -e @world, assuming |
8 |
> all the compiling completes without error, emerge will create packages |
9 |
> for everything that's install. That however takes lots of time. |
10 |
> |
11 |
> I was reading about the quickpkg feature which supposedly creates |
12 |
> packages from what's already installed, but I'm not sure how to |
13 |
> actually run that for a complete system like this. If I put |
14 |
> FEATURES="quickpkg" in make.conf and run emerge -e @world, will emerge |
15 |
> simply make the packages for anything that's already installed, but |
16 |
> not actually compile the packages themselves? |
17 |
> |
18 |
> Thanks, |
19 |
> Mark |
20 |
|
21 |
OK, silly confusion on my part. quickpkg isn't a portage feature, it's |
22 |
a Python script installed as part of portage. |
23 |
|
24 |
Cheers, |
25 |
Mark |