This comment has been minimized.

Yes, of course I can - but when there's about 1000 people a day downloading the Gem, maybe I want to wait until I've finished at the day job so I can deal with the fall out if I make a mistake. Further to that, Jeweler hard codes all the files that should, and shouldn't be included for the sake of easier management I want to come up with a suitable Dir.glob() pattern which can be used to ship gems.

Yes, of course I can - but when there's about 1000 people a day downloading the Gem, maybe I want to wait until I've finished at the day job so I can deal with the fall out if I make a mistake. Further to that, Jeweler hard codes all the files that should, and shouldn't be included for the sake of easier management I want to come up with a suitable Dir.glob() pattern which can be used to ship gems.

This comment has been minimized.

Because Bundler doesn't account for requiring different versions on different platforms, the tests currently don't run under 1.9 (although Cap works) and until i resolve a set of dependencies which is suitable for both, I am reluctant to ship a lock file that might give people ambiguous errors.

Because Bundler doesn't account for requiring different versions on different platforms, the tests currently don't run under 1.9 (although Cap works) and until i resolve a set of dependencies which is suitable for both, I am reluctant to ship a lock file that might give people ambiguous errors.

* Only make deploy:start, deploy:stop, and deploy:restart try sudo as :runner. The other sudo-enabled tasks (deploy:setup, deploy:cleanup, etc.) will now use the :admin_runner user (which by default is unset). [Jamis Buck]