[PATCH Conductor 0/2] Major bundler usage change
Richard Su
rwsu at redhat.com
Fri Jul 20 19:50:11 UTC 2012
On 07/19/2012 11:30 AM, Jason Guiditta wrote:
> Now that I (hopefully) have your attention, this actually makes
> working both upstream as a 'distro developer' simpler, see commit
> message for patch 2 for directions. Crag is also working up
> directions to go in the project README, and eventually we will get the
> website updated as well, though for people just installing RPMs, there
> is 0 change.
>
> The net here is we are going to have a Gemfile in the
> default checkout, making the project behave as a ruby developer would
> expect, with no extra work on their part. Building rpms also does not
> change, so the only thing you as a developer need to make sure you do
> is:
> bundle install --path bundle
> Then, when you add mew gems make sure you update the lock file (you do
> this by simply updating the Gemfile with the new dep, then 'bundle
> install' again, the path is remembered). If you wish to use system
> gems only, mv Gemfile Gemfile.in (just remember to update correctly
> when you create your patch). Please bring any questions/issues to
> list, so others can see any problems you have, and we can make sure to
> catch such scenarios in the README. I am happy to help debug, but if
> we dont capture issues somewhere, they will just happen again.
>
> -j
Ack and pushed. Ran tests for both gem and bundler setup.
I'll submit a patch to update the travis-ci configuration file. The
Gemfile renaming breaks the build.
More information about the aeolus-devel
mailing list