isn't there this neat little gem called bundles that already does exactly that:
bootstrapping a new gem?
Good point. Two points:
1) qk/quick is a "generic" quick starter template tool and, thus,
works for anything e.g. sinatra starter, gli starter, beerdb starter,
jekyll starter and much more.
2) The bundler gem template is "opinionated" - qk/quick offers you
"freedom", that is, more choice for your gem templates. For example, I
prefer to use the "old school" hoe-style to build all gems (80+) e.g.
using a "real" manifest plus some "real" rake files and the .gemspec
gets generated etc. and much more. Try it and see how much better it
is
Sorry for the confusion. Just getting started with some gem examples
for now. Again for some static site (e.g. jekyll) examples, see
mrh/mrhyde [1] (built using qk/quick).
On Aug 18, 2015, at 8:44 PM, Gerald Bauer <gerald.bauer@gmail.com> wrote:
Hello,
isn't there this neat little gem called bundles that already does exactly that:
bootstrapping a new gem?
Good point. Two points:
1) qk/quick is a "generic" quick starter template tool and, thus,
works for anything e.g. sinatra starter, gli starter, beerdb starter,
jekyll starter and much more.
2) The bundler gem template is "opinionated" - qk/quick offers you
"freedom", that is, more choice for your gem templates. For example, I
prefer to use the "old school" hoe-style to build all gems (80+) e.g.
using a "real" manifest plus some "real" rake files and the .gemspec
gets generated etc. and much more. Try it and see how much better it
is
Sorry for the confusion. Just getting started with some gem examples
for now. Again for some static site (e.g. jekyll) examples, see
mrh/mrhyde [1] (built using qk/quick).
Great if bundler works for you. Lucky you. To quote the first
comment/question from your recommended reading:
what gem you created?
I'd say with experience (that is, creating and updating some "real"
gems, for example) you will become more humble. Cheers.
PS: The "classic" about just use a .gemspec titled "Using .gemspecs
as Intended" by Yehuda Katz is here ->
PPS: To find out what you're missing - try the article in the Gem of
the Week series @ Planet Ruby titled "Build, package and publish gems
with hoe rake tasks" -> http://planetruby.github.io/gems/hoe.html
For your convenience here's a list of tasks on offer:
rake announce # publish # Announce your release.
rake audit # test # Run ZenTest against the package.
rake check_extra_deps # deps # Install missing dependencies.
rake check_manifest # debug # Verify the manifest.
rake clean # clean # Clean up all the extras.
rake clobber_docs # publish # Remove RDoc files
rake clobber_package # package # Remove package products
rake config_hoe # debug # Create a fresh ~/.hoerc file.
rake dcov # publish # Generate rdoc coverage report
rake debug_email # publish # Generate email announcement file.
rake debug_gem # debug # Show information about the gem.
rake default # test # Run the default task(s).
rake deps:email # deps # Print a contact list for gems
dependent on this gem
rake deps:fetch # deps # Fetch all the dependent gems
of this gem into tarballs
rake deps:list # deps # List all the dependent gems of this gem
rake docs # publish # Generate rdoc
rake gem # package # Build the gem file hellohoe-0.1.gem
rake generate_key # signing # Generate a key for signing your gems.
rake install_gem # package # Install the package as a gem.
rake install_plugins # deps # Install missing plugins.
rake newb # newb # Install deps, generate docs,
run tests/specs.
rake package # package # Build all the packages
rake post_blog # publish # Post announcement to blog.
rake publish_docs # publish # Publish RDoc to wherever you want.
rake release # package # Package and upload; Requires
VERSION=x.y.z (optional PRE=a.1)
rake release_sanity # package # Sanity checks for release
rake release_to_gemcutter # gemcutter # Push gem to gemcutter.
rake repackage # package # Force a rebuild of the package files
rake ridocs # publish # Generate ri locally for testing.
