| 1 |
On 27/09/2013 06:33, Johann Schmitz wrote: |
| 2 |
> Hi Alan, |
| 3 |
> |
| 4 |
> On 26.09.2013 22:42, Alan McKinnon wrote: |
| 5 |
>> You will break things horribly and will curse the day you tried. |
| 6 |
>> Basically, puppet and portage will get in each other's way and clobber |
| 7 |
>> each other. Puppet has no concept of USE flags worth a damn, cannot |
| 8 |
>> determine in advance what an ebuild will provide and the whole thing |
| 9 |
>> breaks puppet's 100% deterministic model. |
| 10 |
>> |
| 11 |
>> Puppet is designed to work awesomely well with binary distros, that is |
| 12 |
>> where it excels. Keep within those constraints. Same goes for chef, |
| 13 |
>> cfengine and various others things that accomplish the same end. |
| 14 |
> |
| 15 |
> Did you try to combine one of these solutions with portage's binary |
| 16 |
> package feature? With --usepkgonly gentoo is more or less a binary |
| 17 |
> distro. I'm thinking of using a single use flag set for 20+ Gentoo |
| 18 |
> servers to get rid of compiling large packages in the live environment. |
| 19 |
|
| 20 |
|
| 21 |
binpkgs don't turn gentoo into a binary distro, they turn it into |
| 22 |
something resembling a Unix from the 90s with pkgadd - using dumb |
| 23 |
tarballs with no metadata and no room to make choices. Puppet fails at |
| 24 |
that as the intelligence cannot happen in puppet, it has to happen in |
| 25 |
portage. If the binpkg doesn't match what package.* says, puppet is |
| 26 |
stuck and portage falls back to building locally. The result is worse |
| 27 |
than the worst binary distro. |
| 28 |
|
| 29 |
By all means use a central use set, it's what I do for my dev VMs and it |
| 30 |
works out well for me. Just remember to run emerge on each machine |
| 31 |
individually. |
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
Alan McKinnon |
| 38 |
alan.mckinnon@×××××.com |
Archives