Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Does this need hoe as runtime dependency ? #1

Closed
grosser opened this Issue · 10 comments

2 participants

Michael Grosser Austin Ziegler
Michael Grosser

As far as I can see it does not, would be great if it could be removed (development dependency is fine!)

Austin Ziegler
Owner
Michael Grosser

Are you ok with removing hoe and making this use bundler for gem management ?

Austin Ziegler
Owner
Michael Grosser
Michael Grosser

Hope you had a pleasant stay, time for some merge action :)

Austin Ziegler
Owner

I'm not yet convinced. Let me play with it some—I really like what hoe provides a gem developer as a full suite, and I don't see that this is going to replace what I like. I've updated other gems to have hoe as a develop dependency and bring it up to date. I'm going to pull your changes into a branch and play with them before I make a decision.

Austin Ziegler
Owner

I will say that I absolutely don't like the version:bump:patch bit. I don't want a separate file for versioning; I want verification for versioning as hoe's "rake release VERSION=x.y.z" requires.

Michael Grosser

Hmm you do not like blindly releasing a new version ?
I'm more in the other extreme, I don't care what version I release as long as it is a minor/patch bump.
I think it is very useful once you maintain lots of gems, no more need to look at anything, just merge pull request and bump:patch, done :)

Afaik the current best-practice is to have a gem/version.rb so people can check against the version of a dependency, maybe have a look at some of your favorite gems.

But if you want I'll get rid of version.rb and make rake release VERSION=x.y.z work.

Austin Ziegler
Owner

In the hour or so since I started looking at this, I already have the modern-hoe conversion done, plus properly renaming the files that don't look good to .rdoc so they do look good and still create good documentation.

I understand that a lot of gem developers have version.rb files, but that doesn't seem like a best practice to me at all. I do have a number of gems that I maintain sporadically, but I don't want to simple merge pull requests—I have things that I expect from contributions.

BTW, it's much more than just the version:bump:patch thing—I use debug_email, publish_docs, etc. on a regular basis to update the Rubyforge sites (and I just realized that I had not generated such a site for transaction-simple, so…fixed, now).

…and released. Thanks for the push to get this taken care of.

Austin Ziegler halostatue closed this
Michael Grosser

Sounds resonable if you need more then simple release tasks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.