| 1 |
According to man portage: |
| 2 |
|
| 3 |
|
| 4 |
--getbinpkg (-g) |
| 5 |
Using the server and location defined in PORTAGE_BINHOST |
| 6 |
(see make.conf(5)), portage will download the |
| 7 |
information from each binary package found and it will use that |
| 8 |
information to help build the dependency |
| 9 |
list. This option implies -k. (Use -gK for binary-only merging.) |
| 10 |
|
| 11 |
--getbinpkgonly (-G) |
| 12 |
This option is identical to -g, as above, except it will not |
| 13 |
use ANY information from the local machine. |
| 14 |
All binaries will be downloaded from the remote server without |
| 15 |
consulting packages existing in the local |
| 16 |
packages directory. |
| 17 |
|
| 18 |
|
| 19 |
Ok, so what is diference? -g will fetch ALL packages in PORTAGE_BINHOST and use |
| 20 |
them to construct the deps and the other...... |
| 21 |
|
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Gustavo Felisberto |
| 26 |
(HumpBack) |
| 27 |
Web: http://dev.gentoo.org/~humpback |
| 28 |
Blog: http://blog.felisberto.net/ |
| 29 |
------------ |
| 30 |
It's most certainly GNU/Linux, not Linux. Read more at |
| 31 |
http://www.gnu.org/gnu/why-gnu-linux.html . |
| 32 |
------------- |
Archives