diff options
| author | Wincent Colaiuta <win@wincent.com> | 2010-09-03 01:23:15 +0200 |
|---|---|---|
| committer | Santiago Pastorino <santiago@wyeworks.com> | 2010-10-10 14:30:22 -0200 |
| commit | f659a1576fc4a447bbfbd866c7244d8d790a3d9c (patch) | |
| tree | 91f7c6a477c243bb2bfd5f2c6a472d7c7c0d1ccc /actionpack/test/controller/new_base/render_xml_test.rb | |
| parent | d80afed620dde5b9356c883ae187db2332d4c18e (diff) | |
| download | rails-f659a1576fc4a447bbfbd866c7244d8d790a3d9c.tar.gz rails-f659a1576fc4a447bbfbd866c7244d8d790a3d9c.tar.bz2 rails-f659a1576fc4a447bbfbd866c7244d8d790a3d9c.zip | |
Fix misleading advice to add 'memcache' to Gemfile
[#5539 state:committed]
Commit 57144388f removed the hard-coded dependency on the memcache-client
gem, and added this warning advising people to install it if needed. The
problem is, however, that if people follow the advice literally and install
the 'memcache' gem, they will wind up with a completely different thing,
which is not API compatible with the memcache-client gem and which Rails
can't work with.
So, be explicit and tell users to install the 'memcache-client' gem.
Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
Diffstat (limited to 'actionpack/test/controller/new_base/render_xml_test.rb')
0 files changed, 0 insertions, 0 deletions