Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Aug 5, 2008
  1. Use boof's website design for sequel.rubyforge.org

    authored
    Instead of just hosting the RDoc at sequel.rubyforge.org, have an
    actual website, based on boof's design for www.ruby-sequel.org.
    However, drop the Rails project and instead create a plain html site
    generated with a simple script, a single template, and ERB.
    
    Also, add a fifth main feature to the README, showing off the
    improvements coming in 2.4.0.
Commits on Jul 15, 2008
Commits on Jul 7, 2008
  1. Combine sequel and sequel_core into one gem

    authored
    For merging the READMEs, I put the model README at the bottom of the
    core README and used that.
    
    For merging the CHANGELOGs, I merged them manually back to 1.4.0, and
    copied the rest of the model CHANGELOG to the bottom of the file.
    
    Most of the Rakefile code was duplicative, but I think I got
    all tasks except spec_adapters.  I figure few people have all 5
    adapters necessary to run the adapter specs.  I only have 3 of them,
    so I never used spec_adapters.
    
    The specs are still split up so they can be run independently.
    Additionally, the adapter specs are split off from the core specs,
    which helps if you want to put Sequel.connect lines in
    spec_config.rb. The only other spec changes were for path changes.
    
    There weren't conflicts merging anything else, IIRC.
    
    I hope there is no fallout from this.  I haven't noticed any yet,
    running the specs and the test suites for all of my apps that use
    Sequel.
Commits on May 22, 2008
  1. Refactor RDoc creation and options in Rakefiles

    authored
    This should fix the problem of gems not having the correct RDoc options.
    
    The directory structure is changing so that RDoc is now stored in rdoc
    instead of doc/rdoc.  This is because doc is now going to hold
    additional documentation files.
Commits on May 8, 2008
Something went wrong with that request. Please try again.