Comments on: deprec is good, but needs taming.

By: Todd Dickerson

Todd Dickerson — Mon, 20 Apr 2009 15:32:14 +0000

Thanks a ton Mike, this solved my problem EXACTLY! I’ve been looking for a fix for months now.

By: Mike Bailey

Mike Bailey — Mon, 02 Mar 2009 13:30:26 +0000

I generally add only recipes that I need and can’t see it getting too big. If you want to work on a neat solution for excluding recipes I’d be willing to look at including it.

Congratulations on the newborn!

By: Sharad Jain

Sharad Jain — Sun, 01 Mar 2009 02:09:59 +0000

@Mike,
Sorry, I was away with my first newborn.
The 2nd issue is not a problem per se. It’s just a thought that deprec is now manageable but may eventually grow into a rich however unrelated sets of functionalities. That is no different for any general purpose library and can be easily refactored.
Thanks for stopping by.

By: Mike Bailey

Mike Bailey — Thu, 19 Feb 2009 15:07:04 +0000

Your first point is reasonable and has been fixed in deprec-2.0.1. Get it with:

sudo gem install deprec

Newly created ~/.caprc does not load Rails recipes.

This solves the problem of Capistrano’s default deploy tasks having ‘before’ and ‘after’ tasks added when you’re deploying a project that isn’t setup to use deprec.

Existing users can update their existing ~/.caprc, replacing:

require ‘deprec’

with:

require ‘deprec_minus_rails’

I’d love to hear if this solves your first problem. deprec-users@googlegroups.com

Is the second issue you raised causing you any problems or is it a ‘nice to have’?

- Mike