On Fri, 11 Jan 2013 12:32:46 +0000 Adam Spiers <aspiers@suse.com> wrote:
Josef Reidinger (jreidinger@suse.cz) wrote:
On Thu, 10 Jan 2013 19:11:32 +0000 Adam Spiers <aspiers@suse.com> wrote:
Ladislav Slezak (lslezak@suse.cz) wrote:
WebYast also loads some more additional development gems when running from Git checkout (a nice trick, it's convenient for developers and does not affect deployment/RPM build):
https://github.com/webyast/webyast/blob/master/webyast/Gemfile#L63
Yeah, that's a cute trick. It still breaks bundler's guarantee which worries me a bit, but I don't know in practice how bad that is.
Well, there is a lot of notice about this guarantee. I think it is not bad idea, but what I want is ability to switch it off as you need metadata of all gems even those in other groups ( and thats what my patch to bundler does). Reason why I want this is that there is controlled environment where you don't need such guarantee.
First example is bundled gems. You control which gems goes there, you just need to load it.
You mean via "bundle package"? In this case, you already have Gemfile.lock, right? If so, that should already have bundler's "seal of approval", so I agree it should be safe to disable the check.
Second example is our rpms in enterprise products where we release only versions after testing if it works with products. So what I want is only ability to switch this feature off.
This one seems more dangerous to me, since it doesn't prevent us from developing and testing from source with a different set of gem versions to those used when QA is done later in the cycle.
It depends, for webyast and SLMS which I know we run automatic tests in build environment, so it is rebuild and retested automatic with right version of gems. So I don't see much danger here, but of course it require to run tests during build ( that actually for SLMS takes most of its build ). Josef -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org