Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Apr 30, 2011
  1. @wincent

    Shorten description in gemspec

    wincent authored
    The long description looks terrible on the RubyGems.org website, so trim
    it down to the bare minimum.
    
    Signed-off-by: Wincent Colaiuta <win@wincent.com>
  2. @wincent

    Clarify RubyGem description

    wincent authored
    Add a paragraph explaining that Command-T is a Vim plug-in first and
    foremost, and that full functionality is only available when installed
    as a Vim plug-in, but that it is also packaged as a RubyGem so that
    third-party applications can make use of the search algorithm.
  3. @wincent

    Warn about making non-release gems

    wincent authored
    Abbreviating the full version number of an intermediate build (eg.
    "1.1b2-10-g61a374a") to the last tag (eg. "1.1b2") is evil, because it
    means we end up labelling distinct versions of the software with the
    same version number.
    
    Unfortuantely, however, it is a necessary evil because RubyGems will
    choke if passed an intermediate version number:
    
      Invalid gemspec in [command-t.gemspec]: Malformed version number string
      1.1b2-10-g61a374a
      ERROR:  While executing gem ... (NoMethodError)
          undefined method `mark_version' for nil:NilClass
          rake aborted!
    
    So, we resort to using the abbreviated, misleading version number in
    this case. We can at least mitigate this evilness by displaying a
    warning if the user ever tries to build a gem for an intermediate
    release, by adding a dependency on the ":check_tag" task.
    
    Signed-off-by: Wincent Colaiuta <win@wincent.com>
Something went wrong with that request. Please try again.