I thought your response was fine :-) I see what you are saying now - basically that was part of Capistrano already, so moving it to its own gem is a very good idea.<p>I guess I&#x27;m wondering why it needs to be a dependency in Capistrano - is there something in it that Capistrano needs? Wouldn&#x27;t the new gem rely on Capistrano and not the other way around?<p>Regardless, the one lodging the issue probably should have stepped away from the keyboard before lodging the issue. Good on you for maintaining Capistrano, it&#x27;s never an easy job so I hope you get lots of clients who pay you on time and make reasonable requests!