Merge lp:~posulliv/drizzle-interface/ruby-interface into lp:drizzle-interface
Proposed by
Padraig O'Sullivan
Status: | Merged |
---|---|
Merged at revision: | not available |
Proposed branch: | lp:~posulliv/drizzle-interface/ruby-interface |
Merge into: | lp:drizzle-interface |
Diff against target: |
271 lines 11 files modified
INSTALL (+3/-14) Makefile.am (+4/-4) config/install-sh (+2/-3) ruby/CHANGELOG (+3/-0) ruby/LICENSE (+30/-0) ruby/README (+8/-0) ruby/Rakefile (+8/-0) ruby/ext/extconf.rb (+18/-0) ruby/test/setup.rb (+15/-0) ruby/test/test_helper.rb (+16/-0) ruby/test/unit/drizzle_test.rb (+32/-0) |
To merge this branch: | bzr merge lp:~posulliv/drizzle-interface/ruby-interface |
Related bugs: | |
Related blueprints: |
Write Ruby Interface
(Low)
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Monty Taylor | Pending | ||
Review via email: mp+13762@code.launchpad.net |
To post a comment you must log in.
I was messing around with the SWIG generated ruby interface to drizzle tonight and I've started thinking about how we are going to distribute this. I'm guessing we are going to want to create a ruby gem since that seems to be the standard way.
I've created the various files in this branch I'm proposing for a merge for creating a ruby gem and am currently working on writing some unit tests for it. I'm trying to do this in what appears to be the standard way that things like this are done in the ruby community.
How would we distribute something like this? It seems that most ruby folks use github and not launchpad. Is there a way to mirror a launchpad branch on github? What are your plans for the python interface?
Sorry for all the questions on this! Software distribution is something I'm really not familiar with at all.
-Padraig