| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
|
| 5 |
| |
| 6 |
| I glossed over packages a bit, but you get the general idea. I'm not |
| 7 |
| currently using PORTAGE_BINHOST because things are somewhat in flux at |
| 8 |
| the moment. |
| 9 |
| |
| 10 |
|
| 11 |
We've been using PORTAGE_BINHOST for about a year now to manage installs on a couple of |
| 12 |
hundred machines, it seems perfectly stable so far 8). About the only problem with it is |
| 13 |
that if any source built packages have dependencies (we are about 95% binary so theres the |
| 14 |
odd source build required) portage doesn't check the binary repository first, it instantly |
| 15 |
goes off to build from source. That said, the make.conf FEATURES=getbinpkg may get around |
| 16 |
this, I haven't had a chance to try it yet. |
| 17 |
|
| 18 |
C yas |
| 19 |
Baz |
| 20 |
|
| 21 |
|
| 22 |
|
| 23 |
-----BEGIN PGP SIGNATURE----- |
| 24 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 25 |
|
| 26 |
iD8DBQFBionTJvZkjpKMF2wRAqZjAJ9hwoS9BwTySRtYqogKczZy0MJIcgCgq2jX |
| 27 |
M0OwIcV0MN0u099VilNeUb0= |
| 28 |
=AM/J |
| 29 |
-----END PGP SIGNATURE----- |
Archives