Hi Folks,
I’m noticing that the berkshelf gem is listed as a requirement in Gemfiles
of a lot of cookbooks I’ve been working with lately. I suspect that this is
bad behavior now that ChefDK is the recommended deployment method for
berkshelf. Just wanted to confirm with you all that my reasoning is correct.
Hi Folks,
I'm noticing that the berkshelf gem is listed as a requirement in Gemfiles
of a lot of cookbooks I've been working with lately. I suspect that this is
bad behavior now that ChefDK is the recommended deployment method for
berkshelf. Just wanted to confirm with you all that my reasoning is correct.
It's worth mentioning the ChefDk includes gecode libs, pre-built, for
all supported target platforms, which greatly alleviates the
installation heat-cost of Berkshelf.
On machines where this (ChefDK) is not present and the prerequisite
environment variable and system libraries have not been configured, a
full installation of gecode from source will be automatically handled
by the gem (via bundle) installation.
Hi Folks,
I'm noticing that the berkshelf gem is listed as a requirement in Gemfiles
of a lot of cookbooks I've been working with lately. I suspect that this is
bad behavior now that ChefDK is the recommended deployment method for
berkshelf. Just wanted to confirm with you all that my reasoning is correct.
I think both approaches are OK. Depends on whether you want to require
a specific berks version globally (via the ChefDK installation) or you
want to require a specific berks version on a per project level (via
Gemfile).
Usually I tend to prefer the Gemfile approach because it expresses and
enforces all its dependencies. On the other hand, if your README
states that you need ChefDK 0.3.5 as a dependency it's not that bad
either. It's just if your projects have different release cycles and
you don't want to update and test all of them whenever you install a
new ChefDK.
It's worth mentioning the ChefDk includes gecode libs, pre-built, for
all supported target platforms, which greatly alleviates the
installation heat-cost of Berkshelf.
On machines where this (ChefDK) is not present and the prerequisite
environment variable and system libraries have not been configured, a
full installation of gecode from source will be automatically handled
by the gem (via bundle) installation.
Hi Folks,
I'm noticing that the berkshelf gem is listed as a requirement in Gemfiles
of a lot of cookbooks I've been working with lately. I suspect that this is
bad behavior now that ChefDK is the recommended deployment method for
berkshelf. Just wanted to confirm with you all that my reasoning is correct.
Thanks all. That's helpful background and alleviates my concern that a
Gemfile req. would not detect the ChefDK install and try to install it
elsewhere and/or reference a non ChefDK version. But I see how it could be
beneficial to still reference it for some cases.
Happy New Year!
-William
On Wed, Dec 31, 2014 at 4:44 AM, Torben Knerr mail@tknerr.de wrote:
Hi William,
I think both approaches are OK. Depends on whether you want to require
a specific berks version globally (via the ChefDK installation) or you
want to require a specific berks version on a per project level (via
Gemfile).
Usually I tend to prefer the Gemfile approach because it expresses and
enforces all its dependencies. On the other hand, if your README
states that you need ChefDK 0.3.5 as a dependency it's not that bad
either. It's just if your projects have different release cycles and
you don't want to update and test all of them whenever you install a
new ChefDK.
It's worth mentioning the ChefDk includes gecode libs, pre-built, for
all supported target platforms, which greatly alleviates the
installation heat-cost of Berkshelf.
On machines where this (ChefDK) is not present and the prerequisite
environment variable and system libraries have not been configured, a
full installation of gecode from source will be automatically handled
by the gem (via bundle) installation.
Hi Folks,
I'm noticing that the berkshelf gem is listed as a requirement in
Gemfiles
of a lot of cookbooks I've been working with lately. I suspect that
this is
bad behavior now that ChefDK is the recommended deployment method for
berkshelf. Just wanted to confirm with you all that my reasoning is
correct.
Thanks,
William
--
William Jimenez
Systems Engineer, Operations
ItsOn, Inc.
650-241-8470 {us/pacific}
-----Original Message-----
From: AJ Christensen [mailto:aj@junglistheavy.industries]
Sent: Wednesday, December 31, 2014 3:14 AM
To: chef@lists.opscode.com
Subject: [chef] Re: berkshelf gem listed as a requirement in cookbook gemfile
Yo,
Sorry for the follow up.
It's worth mentioning the ChefDk includes gecode libs, pre-built, for all
supported target platforms, which greatly alleviates the installation heat-cost of
Berkshelf.
On machines where this (ChefDK) is not present and the prerequisite
environment variable and system libraries have not been configured, a full
installation of gecode from source will be automatically handled by the gem (via
bundle) installation.
It's problematic to compile. I mentioned this week: it requires a C++ compiler, takes hours on a modest VM or lightweight host, especially if the memory allocated is light, and it can cause other issues if the system runs out of swap and RAM.
Hi Folks,
I'm noticing that the berkshelf gem is listed as a requirement in
Gemfiles of a lot of cookbooks I've been working with lately. I
suspect that this is bad behavior now that ChefDK is the recommended
deployment method for berkshelf. Just wanted to confirm with you all that
my reasoning is correct.