# GemsOnRuby v 0.0.0 (vaporware release / RFP)

**URL:** <https://www.ruby-forum.com/t/gemsonruby-v-0-0-0-vaporware-release-rfp/163544>\
**Category:** Ruby\
**Created:** [March 21, 2009, 7:33pm UTC](https://www.ruby-forum.com/t/gemsonruby-v-0-0-0-vaporware-release-rfp/163544 "2009-03-21T19:33:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![churp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/f14d63/32.png) [@churp](https://www.ruby-forum.com/u/churp)\
**Post date:** [March 21, 2009, 7:33pm UTC](https://www.ruby-forum.com/t/gemsonruby-v-0-0-0-vaporware-release-rfp/163544/1 "2009-03-21T19:33:17Z")

</div>

Hello All,

I am pleased to announce the vaporware release of GemsOnRuby gem,  
currently  
v. 0.0.0  
This is a fork of Dr. Nic’s GemsOnRails, indended for providing the same  
gem-freezing functionality to a ruby application.  
GemsOnRuby can be found in  
GitHub[http://github.com/pjfitzgibbons/gemsonruby/tree](http://github.com/pjfitzgibbons/gemsonruby/tree)and is  
available for  
cloning git://github.com/pjfitzgibbons/gemsonruby.git.

“How can I help?”, you say!!  
Easy, vote +1 or -1 for futher development of this gem… and yes,  
please  
identify existing gems on GitHub or RubyForge that demonstrate  
freezing gems in a standard Ruby application.

Hope you all like the happy-programming vapo-action!!

Peter F.  
(847) 687-7646  
Email: removed\_email\_address@domain.invalid  
IM GTalk: peter.fitzgibbons  
IM Yahoo: pjfitzgibbons  
IM MSN: removed\_email\_address@domain.invalid  
IM AOL: removed\_email\_address@domain.invalid

---

<div class="post-metadata">

**Author:** ![churp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/f14d63/32.png) [@churp](https://www.ruby-forum.com/u/churp)\
**Post date:** [March 21, 2009, 8:14pm UTC](https://www.ruby-forum.com/t/gemsonruby-v-0-0-0-vaporware-release-rfp/163544/2 "2009-03-21T20:14:16Z")

</div>

On Sat, Mar 21, 2009 at 7:29 PM, Peter F.  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> “How can I help?”, you say!!  
> Easy, vote +1 or -1 for futher development of this gem… and yes, please  
> identify existing gems on GitHub or RubyForge that demonstrate  
> freezing gems in a standard Ruby application.

How it is different from dr. Nic GemsOnRails project? I see only dr.  
Nic commits there…

–  
Pozdrawiam

Rados³aw Bu³at  
[http://radarek.jogger.pl](http://radarek.jogger.pl) - mój blog

---

<div class="post-metadata">

**Author:** ![churp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/f14d63/32.png) [@churp](https://www.ruby-forum.com/u/churp)\
**Post date:** [March 23, 2009, 10:46pm UTC](https://www.ruby-forum.com/t/gemsonruby-v-0-0-0-vaporware-release-rfp/163544/3 "2009-03-23T22:46:37Z")

</div>

On Mar 21, 2009, at 11:29, Peter F. wrote:

> This is a fork of Dr. Nic’s GemsOnRails, indended for providing the  
> same  
> gem-freezing functionality to a ruby application.

How is this different than:

gem unpack gemname

Then adding the gemname-version/lib to $LOAD\_PATH where appropriate.

Then checking in?

---

<div class="post-metadata">

**Author:** ![churp](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/f14d63/32.png) [@churp](https://www.ruby-forum.com/u/churp)\
**Post date:** [March 21, 2009, 9:48pm UTC](https://www.ruby-forum.com/t/gemsonruby-v-0-0-0-vaporware-release-rfp/163544/4 "2009-03-21T21:48:33Z")

</div>

Being v. 0.0.0, I haven’t actually changed anything from the fork. 🙂

GemsOnRails is tied and exclusively compatible with a Rails  
implementation.

GemsOnRuby will be able to be “easily :)” applied to a plain Ruby app  
containing not-much-more than a main.rb (or other starting point) and a  
./lib directory.

🙂

Peter F.  
(847) 687-7646  
Email: removed\_email\_address@domain.invalid  
IM GTalk: peter.fitzgibbons  
IM Yahoo: pjfitzgibbons  
IM MSN: removed\_email\_address@domain.invalid  
IM AOL: removed\_email\_address@domain.invalid

2009/3/21 RadosÅ‚aw BuÅ‚at [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)
