Now you can take any library or Rails plugin or command line
application, gemify it, and easily share it with the Ruby world.
With gems you get in-built version support (you can specify which
version of a gem you want when you use it via the require_gem method),
an encapsulated, consistent folder structure for your bin/lib/test
folders, and you get cross-platform support for bin apps. Too much
niftiness to ignore, really.
The New Gem Generator is like the rails command for rails applications,
but it creates the folders and starting files for a new gem. It’s called
newgem.
This is great. You're cooking up one sweet Ruby library after another.
Calling it "gemify" isn't an option? Sounds sweeter.
···
On 10/11/06, Dr Nic <drnicwilliams@gmail.com> wrote:
Now you can take any library or Rails plugin or command line
application, gemify it, and easily share it with the Ruby world.
With gems you get in-built version support (you can specify which
version of a gem you want when you use it via the require_gem method),
an encapsulated, consistent folder structure for your bin/lib/test
folders, and you get cross-platform support for bin apps. Too much
niftiness to ignore, really.
The New Gem Generator is like the rails command for rails applications,
but it creates the folders and starting files for a new gem. It's called
newgem.
This is great. You're cooking up one sweet Ruby library after another.
Calling it "gemify" isn't an option? Sounds sweeter.
Unfortunately all voting on project names happens before the project is
released. That is, I voted alone between: newgem, gemnew, new_gem,
gem_new. You get the jist of my unimaginative options.
I like gemify as a command name though. Perhaps I'll add it in the bin
folder as a duplicate, just for you
I never knew it existed, but if your users can't type the words "gem
install <yourproject>" then running the setup.rb script for your library
will make them very happy.
I never knew it existed, but if your users can't type the words "gem
install <yourproject>" then running the setup.rb script for your library
will make them very happy.
step 2)---> newgem <gem name>
here it creates the folder successfully with the name i gave, n it
allows the manipulation which is required by me.
here comes my problem???
step 3)—> rake package
while creating a gem with the "rake package command", I came across an
error saying "could'nt find HOME environment --expanding '~/hoerc'"
which is followed by number of error lines…
