Permalink
Browse files

move the require_path back to where it was with a comment

  • Loading branch information...
1 parent 8166957 commit 4f152c9bce124e024e9d779def06190e3aa20341 @knzconnor knzconnor committed Apr 6, 2010
Showing with 4 additions and 1 deletion.
  1. +4 −1 NAME.gemspec
View
@@ -8,7 +8,6 @@ Gem::Specification.new do |s|
s.specification_version = 2 if s.respond_to? :specification_version=
s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
s.rubygems_version = '1.3.5'
- s.require_paths = %w[lib]
## Leave these as is they will be modified for you by the rake gemspec task.
## If your rubyforge_project name is different, then edit it and comment out
@@ -30,6 +29,10 @@ Gem::Specification.new do |s|
s.email = 'jdoe@example.com'
s.homepage = 'http://example.com/NAME'
+ ## This gets added to the $LOAD_PATH so that 'lib/NAME.rb' can be required as
+ ## require 'NAME.rb' or'/lib/NAME/file.rb' can be as require 'NAME/file.rb'
+ s.require_paths = %w[lib]
+
## This sections is only necessary if you have C extensions.
s.require_paths << 'ext'
s.extensions = %w[ext/extconf.rb]

0 comments on commit 4f152c9

Please sign in to comment.