judofyr / gemify

The lightweight gemspec editor.

Gemify, the gemspec generator

Overview

Gemify is a simple tool which helps you generate gemspecs (which are used for building gems) and verify that your project follows the common and proven way to structure your Ruby packages.

Getting started

Generating gemspec:

$ gem install gemify
$ cd myproject (which doesn't have a gemspec yet)
$ gemify
Gemify needs to know a bit about your project, but should be
able to guess most of the information. Type the value if you
need to correct it, or press ENTER to accept the suggestion by Gemify.

Project name:        gemify? 
Namespace:           Gemify? 
Library:             lib/gemify? 

*** Verifying the structure of lib/
[+] Please consider to define Gemify::VERSION in lib/gemify/version.rb
[.] Done

*** Verifying the structure of bin/
[.] Done

*** Verifying the structure of ext/
[.] Done

*** Generating a gemspec
[.] Done

Please open gemify.gemspec in your text editor and fill out the details.

You should fix any warnings that was reported above. You won't need to
generate a new gemspec after you've fixed them.

You must also define Gemify::VERSION in lib/gemify/version.rb.
Gemify has automatically created the file for you, so simply
open it in your text editor and fill in the current version.

Or if you just want to verify it:

$ gemify -v

Build and share a gem

Let's not reinvent the wheel, shall we?

$ gem build foo.gemspec
$ gem push foo.gem

Acknowledgements

Thanks to Pat Nakajima for reminding me that Gemify still has its uses.

Contributors

• David A. Cuadrado
• Ben Wyrosdick
• Chris Wanstrath
• Pat Nakajima
• Vincent Landgraf

gemify's Issues

Use Readline

Ships with Ruby, no reason to not use it. Would also be cool to get tab-completion for dependencies.

Change current behaviour: gemify should not create a *_version.rb file unasked

Hi,

Right now gemify automatically creates a new version.rb file in my project.

This is annoying. I dont want gemify to ever make a file that I dont allow or instructed it to do so.

Can it perhaps be changed that gemify asks before it creates the file? Or a configuration option,
that can be toggled (and turned off permanently too when the user wants to)?

gemify shouldn't replace dynamic content.

hey

I'm trying out gemify because I like the idea and so far so good but I don't think gemify should replace dynamic content. For example:

   s.version = Project::VERSION
   s.post_install_message = <<-EXAMPLE
   #{Project::VERSION}
   EXAMPLE

I would like content like that to remain dynamic as I don't want to manually replace every
occurrence of Project::VERSION by myself after using gemify. As it stands, gemfiy doesn't facilitate that.

EDIT: I'm using gemify -u to re-generate the gemspec. Right now I'm only using gemify to maintain Gem::Specification#files and Gem::Specification#test_files

Thanks,
Rob

Should just use .gemspec file instead of .gemify

Shouldn't be too tough, since .gemify is so close the the gemspec anywayz.

Invoke multiple tasks at the same prompt

If you write 123sx it should ask you for the name, the summary and the version before saving and quitting.

Make it possible to set both development and runtime dependencies

Feature request: Gemify adds to #test_files

Hey

gemify -u is great but it doesn't seem to try to make any attempt to add to Gem::Specification#test_files=

It'd be cool if it did? maybe anything matching test/**/*.rb or spec/**/*.rb

Thanks