Red Hat Bugzilla – Bug 817641
Document how to use Redhat rubygems with letters in version string
Last modified: 2015-08-06 01:54:26 EDT
Description of problem:
Document how to use Redhat rubygems artifacts which are need to use letters in version string to differentiate with regarding to community releases.
we will use community version as the basement
and redhat as string qualifier and build number for easy recognition for repeated builds.
example result: 2.0.1.redhat.1
Assuming that the user has an exploded local copy of our torquebox-rubygems-repo.zip, or an internally-hosted repository (akin to internal hosting of the WFK maven repo), the user who installs gems manually can use a command involving the --pre flag with a generic name
gem install --pre torquebox-messaging
I think it may also be possible (needs verification) to skip the --pre flag and specify just a distinct -v for version
gem install torquebox-messaging -v 2.0.2.redhat.1
Without these steps, assuming the user includes RubyGems.org (akin to Maven central), the community versions will be grabbed, as RubyGems.org hosts them, and they are considered non-pre.
For users using Gemfiles, they can add the appropriate source URL, and version specifier. The "spermy" operator may be used to selectively grab the latest 2.0.2.redhat.WHATEVER version.
# Source to user-hosted repository
# Regular RubyGems.org central repository
# Grab a very specific version of 2.0.2.redhat.1
gem "torquebox-messaging", '2.0.2.redhat.1'
# Grab the "latest" 2.0.2.redhat series
gem "torquebox-capistrano-support", '~> 2.0.0.redhat'
# Use rails from RubyGems.org
gem "rails", '3.1.1'
please add this documentation note to TorqueBox docs
Sorry, guys, what do I actually need to document, and where in the TB guide should it go?
I would say that it should be somewhere in installation section of TB reference guide and probably in RN too. Bob, what do you think?
The text from my comment (#1) should be included in the installation notes, alongside Ben's README from https://bugzilla.redhat.com/show_bug.cgi?id=828165
Closed, verified as a part of final TB documentation.