[PATCH 0/3] Bundler usage changes Rev 2

Jason Guiditta jguiditt at redhat.com
Wed May 16 21:27:49 UTC 2012


[PATCH conductor 1/3] Redmine #3241: Add small extension library to
[PATCH conductor 2/3] Redmine #3242: Set up conductor to use new

This last one is not meant to be pushed, and is simply here if you hit any issues 
to help with debugging, feel free to not apply it unless you hit problems.
[PATCH conductor 3/3] WIP: add some logging to debug libraries that

This patchset implements Redmine feature #3162: 'As a developer, I would
like to be able to easily work using rubygem or rpm, and to be able to
swap back and forth, so that I can more easily test/develop against
different platforms'.  Note that there seems to be a lingering issues with
what bundler see on an install where USE_BUNDLER=yes.  In my testing, something
on the path was looking for rack ~> 1.2.1, but I cannot for the ife of me
figure out what.  This does not keep the distro/rpm version from working, and I
believe it is a bug outside these patches' scope, so I just want to mention
that seems to be the only remaining blocker for upstream.

Testing of this set for standard rpm-only development is as usual:
* make sure you can run tests from src
* install rpm and verify things work
* make sure you can run a dev-mode server as expected

None of the above should show any calls to bunlder or 'bundle exec'.  If they do,
there is a bug in these patches.

To test upstream, you need a clean env (perhaps via rvm and a gemset).  You then set
the following env var:
* USE_BUNDLER=yes

Then run:
(you need to cp Gemfile.in -> Gemfile first for this step, and do this from src dir,
or specify full path)
* bundle install

This should install the the versions in our Gemfile.lock.  Try to run tests:

* rake spec

This is where I hit the bad dep.  Any assistance figuring out why is appreciated,
though I think I have made prgress tracking it down (and hope to have a patch to fix 
the lockfile tomorrow).

-j




More information about the aeolus-devel mailing list