Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Fix misleading advice to add 'memcache' to Gemfile

#5539

Commit 57144388f removed the hard-coded dependency on the memcache-client gem, and added a 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.

Patches against master and 3-0-stable attached.

Reported by Wincent Colaiuta · September 3rd, 2010 @ 12:27 AM

State: committed
Milestone: none
Assigned to: Santiago Pastorino Santiago Pastorino
Importance: Low

Activity

  1. Jeff Kreeftmeijer
    Jeff Kreeftmeijer
    • Tag set to memcache, patch, warning
    • Importance changed from to Low

    This message never told you to put "memcache" in your Gemfile. It said you don't have a thing called "memcache" installed. I understand how this can be misleading, though.

    +1

    October 10th, 2010 @ 08:39 AM

  2. Wincent Colaiuta
    Wincent Colaiuta

    No, it did tell you to put "memcache" in your Gemfile; read what it says:

    You don't have memcache installed in your application. Please add it to your Gemfile

    Please at "it" to your Gemfile, where "it" here can only refer to "memcache".

    October 10th, 2010 @ 10:41 AM

  3. Jeff Kreeftmeijer
    Jeff Kreeftmeijer

    Again, I know it was misleading, but it told you to require memcache (the library), not to add "memcache" (the string) to your Gemfile. I completely agree with your patch, though. :)

    October 10th, 2010 @ 12:08 PM

  4. Jeff Kreeftmeijer
    Jeff Kreeftmeijer
    • Title changed from [PATCH] Fix misleading advice to add 'memcache' to Gemfile to Fix misleading advice to add 'memcache' to Gemfile

    October 10th, 2010 @ 12:08 PM

  5. Wincent Colaiuta
    Wincent Colaiuta

    it told you to require memcache (the library), not to add "memcache" (the string) to your Gemfile.

    So, you're saying that "Please add it to your Gemfile" means "Require it". Rubbish.

    October 10th, 2010 @ 12:21 PM

  6. Repository
    Repository
    • State changed from new to committed

    (from [f659a1576fc4a447bbfbd866c7244d8d790a3d9c]) Fix misleading advice to add 'memcache' to Gemfile

    [#5539 Fix misleading advice to add 'memcache' to Gemfile 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
    http://github.com/rails/rails/commit/f659a1576fc4a447bbfbd866c7244d...

    October 10th, 2010 @ 05:30 PM

  7. Repository
    Repository

    (from [3a6acb616235349f829236ec04a182d27fe2d397]) Fix misleading advice to add 'memcache' to Gemfile

    [#5539 Fix misleading advice to add 'memcache' to Gemfile 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
    http://github.com/rails/rails/commit/3a6acb616235349f829236ec04a182...

    October 10th, 2010 @ 05:30 PM

  8. Ryan Bigg
    Ryan Bigg
    • Tag cleared.

    Automatic cleanup of spam.

    October 11th, 2010 @ 12:09 PM