According to man portage:
--getbinpkg (-g)
Using the server and location defined in PORTAGE_BINHOST
(see make.conf(5)), portage will download the
information from each binary package found and it will use that
information to help build the dependency
list. This option implies -k. (Use -gK for binary-only merging.)
--getbinpkgonly (-G)
This option is identical to -g, as above, except it will not
use ANY information from the local machine.
All binaries will be downloaded from the remote server without
consulting packages existing in the local
packages directory.
Ok, so what is diference? -g will fetch ALL packages in PORTAGE_BINHOST and use
them to construct the deps and the other......
--
Gustavo Felisberto
(HumpBack)
Web: http://dev.gentoo.org/~humpback
Blog: http://blog.felisberto.net/
------------
It's most certainly GNU/Linux, not Linux. Read more at
http://www.gnu.org/gnu/why-gnu-linux.html .
-------------
--getbinpkg (-g)
Using the server and location defined in PORTAGE_BINHOST
(see make.conf(5)), portage will download the
information from each binary package found and it will use that
information to help build the dependency
list. This option implies -k. (Use -gK for binary-only merging.)
--getbinpkgonly (-G)
This option is identical to -g, as above, except it will not
use ANY information from the local machine.
All binaries will be downloaded from the remote server without
consulting packages existing in the local
packages directory.
Ok, so what is diference? -g will fetch ALL packages in PORTAGE_BINHOST and use
them to construct the deps and the other......
--
Gustavo Felisberto
(HumpBack)
Web: http://dev.gentoo.org/~humpback
Blog: http://blog.felisberto.net/
------------
It's most certainly GNU/Linux, not Linux. Read more at
http://www.gnu.org/gnu/why-gnu-linux.html .
-------------