bundler 0.8.1 → 0.9.0.pre1

data/lib/bundler/vendor/thor/util.rb

@@ -0,0 +1,233 @@
+require 'rbconfig'
+
+class Thor
+  module Sandbox #:nodoc:
+  end
+
+  # This module holds several utilities:
+  #
+  # 1) Methods to convert thor namespaces to constants and vice-versa.
+  #
+  #   Thor::Utils.namespace_from_thor_class(Foo::Bar::Baz) #=> "foo:bar:baz"
+  #
+  # 2) Loading thor files and sandboxing:
+  #
+  #   Thor::Utils.load_thorfile("~/.thor/foo")
+  #
+  module Util
+
+    # Receives a namespace and search for it in the Thor::Base subclasses.
+    #
+    # ==== Parameters
+    # namespace<String>:: The namespace to search for.
+    #
+    def self.find_by_namespace(namespace)
+      namespace = "default#{namespace}" if namespace.empty? || namespace =~ /^:/
+
+      Thor::Base.subclasses.find do |klass|
+        klass.namespace == namespace
+      end
+    end
+
+    # Receives a constant and converts it to a Thor namespace. Since Thor tasks
+    # can be added to a sandbox, this method is also responsable for removing
+    # the sandbox namespace.
+    #
+    # This method should not be used in general because it's used to deal with
+    # older versions of Thor. On current versions, if you need to get the
+    # namespace from a class, just call namespace on it.
+    #
+    # ==== Parameters
+    # constant<Object>:: The constant to be converted to the thor path.
+    #
+    # ==== Returns
+    # String:: If we receive Foo::Bar::Baz it returns "foo:bar:baz"
+    #
+    def self.namespace_from_thor_class(constant, remove_default=true)
+      constant = constant.to_s.gsub(/^Thor::Sandbox::/, "")
+      constant = snake_case(constant).squeeze(":")
+      constant.gsub!(/^default/, '') if remove_default
+      constant
+    end
+
+    # Given the contents, evaluate it inside the sandbox and returns the
+    # namespaces defined in the sandbox.
+    #
+    # ==== Parameters
+    # contents<String>
+    #
+    # ==== Returns
+    # Array[Object]
+    #
+    def self.namespaces_in_content(contents, file=__FILE__)
+      old_constants = Thor::Base.subclasses.dup
+      Thor::Base.subclasses.clear
+
+      load_thorfile(file, contents)
+
+      new_constants = Thor::Base.subclasses.dup
+      Thor::Base.subclasses.replace(old_constants)
+
+      new_constants.map!{ |c| c.namespace }
+      new_constants.compact!
+      new_constants
+    end
+
+    # Returns the thor classes declared inside the given class.
+    #
+    def self.thor_classes_in(klass)
+      stringfied_constants = klass.constants.map { |c| c.to_s }
+      Thor::Base.subclasses.select do |subclass|
+        next unless subclass.name
+        stringfied_constants.include?(subclass.name.gsub("#{klass.name}::", ''))
+      end
+    end
+
+    # Receives a string and convert it to snake case. SnakeCase returns snake_case.
+    #
+    # ==== Parameters
+    # String
+    #
+    # ==== Returns
+    # String
+    #
+    def self.snake_case(str)
+      return str.downcase if str =~ /^[A-Z_]+$/
+      str.gsub(/\B[A-Z]/, '_\&').squeeze('_') =~ /_*(.*)/
+      return $+.downcase
+    end
+
+    # Receives a string and convert it to camel case. camel_case returns CamelCase.
+    #
+    # ==== Parameters
+    # String
+    #
+    # ==== Returns
+    # String
+    #
+    def self.camel_case(str)
+      return str if str !~ /_/ && str =~ /[A-Z]+.*/
+      str.split('_').map { |i| i.capitalize }.join
+    end
+
+    # Receives a namespace and tries to retrieve a Thor or Thor::Group class
+    # from it. It first searches for a class using the all the given namespace,
+    # if it's not found, removes the highest entry and searches for the class
+    # again. If found, returns the highest entry as the class name.
+    #
+    # ==== Examples
+    #
+    #   class Foo::Bar < Thor
+    #     def baz
+    #     end
+    #   end
+    #
+    #   class Baz::Foo < Thor::Group
+    #   end
+    #
+    #   Thor::Util.namespace_to_thor_class("foo:bar")     #=> Foo::Bar, nil # will invoke default task
+    #   Thor::Util.namespace_to_thor_class("baz:foo")     #=> Baz::Foo, nil
+    #   Thor::Util.namespace_to_thor_class("foo:bar:baz") #=> Foo::Bar, "baz"
+    #
+    # ==== Parameters
+    # namespace<String>
+    #
+    # ==== Errors
+    # Thor::Error:: raised if the namespace cannot be found.
+    #
+    # Thor::Error:: raised if the namespace evals to a class which does not
+    #               inherit from Thor or Thor::Group.
+    #
+    def self.namespace_to_thor_class_and_task(namespace, raise_if_nil=true)
+      if namespace.include?(?:)
+        pieces = namespace.split(":")
+        task   = pieces.pop
+        klass  = Thor::Util.find_by_namespace(pieces.join(":"))
+      end
+
+      unless klass
+        klass, task = Thor::Util.find_by_namespace(namespace), nil
+      end
+
+      raise Error, "could not find Thor class or task '#{namespace}'" if raise_if_nil && klass.nil?
+      return klass, task
+    end
+
+    # Receives a path and load the thor file in the path. The file is evaluated
+    # inside the sandbox to avoid namespacing conflicts.
+    #
+    def self.load_thorfile(path, content=nil)
+      content ||= File.binread(path)
+
+      begin
+        Thor::Sandbox.class_eval(content, path)
+      rescue Exception => e
+        $stderr.puts "WARNING: unable to load thorfile #{path.inspect}: #{e.message}"
+      end
+    end
+
+    def self.user_home
+      @@user_home ||= if ENV["HOME"]
+        ENV["HOME"]
+      elsif ENV["USERPROFILE"]
+        ENV["USERPROFILE"]
+      elsif ENV["HOMEDRIVE"] && ENV["HOMEPATH"]
+        File.join(ENV["HOMEDRIVE"], ENV["HOMEPATH"])
+      elsif ENV["APPDATA"]
+        ENV["APPDATA"]
+      else
+        begin
+          File.expand_path("~")
+        rescue
+          if File::ALT_SEPARATOR
+            "C:/"
+          else
+            "/"
+          end
+        end
+      end
+    end
+
+    # Returns the root where thor files are located, dependending on the OS.
+    #
+    def self.thor_root
+      File.join(user_home, ".thor").gsub(/\\/, '/')
+    end
+
+    # Returns the files in the thor root. On Windows thor_root will be something
+    # like this:
+    #
+    #   C:\Documents and Settings\james\.thor
+    #
+    # If we don't #gsub the \ character, Dir.glob will fail.
+    #
+    def self.thor_root_glob
+      files = Dir["#{thor_root}/*"]
+
+      files.map! do |file|
+        File.directory?(file) ? File.join(file, "main.thor") : file
+      end
+    end
+
+    # Where to look for Thor files.
+    #
+    def self.globs_for(path)
+      ["#{path}/Thorfile", "#{path}/*.thor", "#{path}/tasks/*.thor", "#{path}/lib/tasks/*.thor"]
+    end
+
+    # Return the path to the ruby interpreter taking into account multiple
+    # installations and windows extensions.
+    #
+    def self.ruby_command
+      @ruby_command ||= begin
+        ruby = File.join(Config::CONFIG['bindir'], Config::CONFIG['ruby_install_name'])
+        ruby << Config::CONFIG['EXEEXT']
+
+        # escape string in case path to ruby executable contain spaces.
+        ruby.sub!(/.*\s.*/m, '"\&"')
+        ruby
+      end
+    end
+
+  end
+end

data/lib/bundler/vendor/thor/version.rb

@@ -0,0 +1,3 @@
+class Thor
+  VERSION = "0.12.2".freeze
+end

metadata

@@ -1,55 +1,77 @@
 --- !ruby/object:Gem::Specification 
 name: bundler
 version: !ruby/object:Gem::Version 
-  version: 0.8.1
+  version: 0.9.0.pre1
 platform: ruby
 authors: 
-- Yehuda Katz
 - Carl Lerche
+- Yehuda Katz
 autorequire: 
 bindir: bin
 cert_chain: []
 
-date: 2010-01-05 00:00:00 -08:00
+date: 2010-01-30 00:00:00 -08:00
 default_executable: 
 dependencies: []
 
-description: An easy way to vendor gem dependencies
+description: 
 email: 
-- wycats@gmail.com
-- clerche@engineyard.com
-executables: []
-
+- carlhuda@engineyard.com
+executables: 
+- bundle
 extensions: []
 
-extra_rdoc_files: 
-- README.markdown
-- LICENSE
+extra_rdoc_files: []
+
 files: 
-- LICENSE
-- README.markdown
-- Rakefile
-- lib/bundler/bundle.rb
+- bin/bundle
 - lib/bundler/cli.rb
-- lib/bundler/commands/bundle_command.rb
-- lib/bundler/commands/exec_command.rb
+- lib/bundler/definition.rb
 - lib/bundler/dependency.rb
 - lib/bundler/dsl.rb
 - lib/bundler/environment.rb
-- lib/bundler/finder.rb
-- lib/bundler/gem_bundle.rb
-- lib/bundler/gem_ext.rb
+- lib/bundler/index.rb
+- lib/bundler/installer.rb
 - lib/bundler/remote_specification.rb
 - lib/bundler/resolver.rb
-- lib/bundler/runtime.rb
+- lib/bundler/rubygems.rb
 - lib/bundler/source.rb
-- lib/bundler/templates/app_script.erb
+- lib/bundler/specification.rb
 - lib/bundler/templates/environment.erb
-- lib/bundler/templates/environment_picker.erb
+- lib/bundler/templates/Gemfile
+- lib/bundler/ui.rb
+- lib/bundler/vendor/thor/actions/create_file.rb
+- lib/bundler/vendor/thor/actions/directory.rb
+- lib/bundler/vendor/thor/actions/empty_directory.rb
+- lib/bundler/vendor/thor/actions/file_manipulation.rb
+- lib/bundler/vendor/thor/actions/inject_into_file.rb
+- lib/bundler/vendor/thor/actions.rb
+- lib/bundler/vendor/thor/base.rb
+- lib/bundler/vendor/thor/core_ext/file_binary_read.rb
+- lib/bundler/vendor/thor/core_ext/hash_with_indifferent_access.rb
+- lib/bundler/vendor/thor/core_ext/ordered_hash.rb
+- lib/bundler/vendor/thor/error.rb
+- lib/bundler/vendor/thor/group.rb
+- lib/bundler/vendor/thor/invocation.rb
+- lib/bundler/vendor/thor/parser/argument.rb
+- lib/bundler/vendor/thor/parser/arguments.rb
+- lib/bundler/vendor/thor/parser/option.rb
+- lib/bundler/vendor/thor/parser/options.rb
+- lib/bundler/vendor/thor/parser.rb
+- lib/bundler/vendor/thor/rake_compat.rb
+- lib/bundler/vendor/thor/runner.rb
+- lib/bundler/vendor/thor/shell/basic.rb
+- lib/bundler/vendor/thor/shell/color.rb
+- lib/bundler/vendor/thor/shell.rb
+- lib/bundler/vendor/thor/task.rb
+- lib/bundler/vendor/thor/util.rb
+- lib/bundler/vendor/thor/version.rb
+- lib/bundler/vendor/thor.rb
 - lib/bundler.rb
-- lib/rubygems_plugin.rb
+- LICENSE
+- README
 has_rdoc: true
-homepage: http://github.com/wycats/bundler
+homepage: http://github.com/carlhuda/bundler
 licenses: []
 
 post_install_message: 
@@ -75,6 +97,6 @@ rubyforge_project:
 rubygems_version: 1.3.5
 signing_key: 
 specification_version: 3
-summary: An easy way to vendor gem dependencies
+summary: Bundles are fun
 test_files: []
 

data/README.markdown

@@ -1,284 +0,0 @@
-## Bundler : A gem to bundle gems
-
-    Github:       http://github.com/wycats/bundler
-    Mailing list: http://groups.google.com/group/ruby-bundler
-    IRC:          #carlhuda on freenode
-
-## Intro
-
-Bundler is a tool that manages gem dependencies for your ruby application. It
-takes a gem manifest file and is able to fetch, download, and install the gems
-and all child dependencies specified in this manifest. It can manage any update
-to the gem manifest file and update the bundled gems accordingly. It also lets
-you run any ruby code in context of the bundled gem environment.
-
-## Installation
-
-Bundler has no dependencies. Just clone the git repository and install the gem
-with the following rake task:
-
-    rake install
-
-You can also install the gem with
-
-    gem install bundler
-
-## Usage
-
-Bundler requires a gem manifest file to be created. This should be a file named
-`Gemfile` located in the root directory of your application. After the manifest
-has been created, in your shell, cd into your application's directory and run
-`gem bundle`. This will start the bundling process.
-
-### Manifest file
-
-This is where you specify all of your application's dependencies. By default
-this should be in a file named `Gemfile` located in your application's root
-directory. The following is an example of a potential `Gemfile`. For more
-information, please refer to Bundler::ManifestBuilder.
-
-    # Specify a dependency on rails. When the bundler downloads gems,
-    # it will download rails as well as all of rails' dependencies (such as
-    # activerecord, actionpack, etc...)
-    #
-    # At least one dependency must be specified
-    gem "rails"
-
-    # Specify a dependency on rack v.1.0.0. The version is optional. If present,
-    # it can be specified the same way as with rubygems' #gem method.
-    gem "rack", "1.0.0"
-
-    # Specify a dependency rspec, but only require that gem in the "testing"
-    # environment. :except is also a valid option to specify environment
-    # restrictions.
-    gem "rspec", :only => :testing
-
-    # Specify a dependency, but specify that it is already present and expanded
-    # at vendor/rspec. Bundler will treat rspec as though it was the rspec gem
-    # for the purpose of gem resolution: if another gem depends on a version
-    # of rspec satisfied by "1.1.6", it will be used.
-    #
-    # If a gemspec is found in the directory, it will be used to specify load
-    # paths and supply additional dependencies.
-    #
-    # Bundler will also recursively search for *.gemspec, and assume that
-    # gemspecs it finds represent gems that are rooted in the same directory
-    # the gemspec is found in.
-    gem "rspec", "1.1.6", :vendored_at => "vendor/rspec"
-
-    # You can also control what will happen when you run Bundler.require_env
-    # by using the :require_as option, as per the next two examples.
-
-    # Don't auto-require this gem.
-    gem "rspec-rails", "1.2.9", :require_as => nil
-
-    # Require something other than the default.
-    gem "yajl-ruby", "0.6.7", :require_as => "yajl/json_gem"
-
-    # Works exactly like :vendored_at, but first downloads the repo from
-    # git and handles stashing the files for you. As with :vendored_at,
-    # Bundler will automatically use *.gemspec files in the root or anywhere
-    # in the repository.
-    gem "rails", "3.0.pre", :git => "git://github.com/rails/rails.git"
-
-    # Add http://gems.github.com as a source that the bundler will use
-    # to find gems listed in the manifest. By default,
-    # http://gems.rubyforge.org is already added to the list.
-    #
-    # This is an optional setting.
-    source "http://gems.github.com"
-
-    # Specify where the bundled gems should be stashed. This directory will
-    # be a gem repository where all gems are downloaded to and installed to.
-    #
-    # This is an optional setting.
-    # The default is: vendor/gems
-    bundle_path "my/bundled/gems"
-
-    # Specify where gem executables should be copied to.
-    #
-    # This is an optional setting.
-    # The default is: bin
-    bin_path "my/executables"
-
-    # Specify that rubygems should be completely disabled. This means that it
-    # will be impossible to require it and that available gems will be
-    # limited exclusively to gems that have been bundled.
-    #
-    # The default is to automatically require rubygems. There is also a
-    # `disable_system_gems` option that will limit available rubygems to
-    # the ones that have been bundled.
-    disable_rubygems
-
-### Gem Resolution
-
-One of the most important things that the bundler does is do a
-dependency resolution on the full list of gems that you specify, all
-at once. This differs from the one-at-a-time dependency resolution that
-Rubygems does, which can result in the following problem:
-
-    # On my system:
-    #   activesupport 3.0.pre
-    #   activesupport 2.3.4
-    #   activemerchant 1.4.2
-    #   rails 2.3.4
-    #
-    # activemerchant 1.4.2 depends on activesupport >= 2.3.2
-
-    gem "activemerchant", "1.4.2"
-    # results in activating activemerchant, as well as
-    # activesupport 3.0.pre, since it is >= 2.3.2
-
-    gem "rails", "2.3.4"
-    # results in:
-    #   can't activate activesupport (= 2.3.4, runtime)
-    #   for ["rails-2.3.4"], already activated
-    #   activesupport-3.0.pre for ["activemerchant-1.4.2"]
-
-This is because activemerchant has a broader dependency, which results
-in the activation of a version of activesupport that does not satisfy
-a more narrow dependency.
-
-Bundler solves this problem by evaluating all dependencies at once,
-so it can detect that all gems *together* require activesupport "2.3.4".
-
-### Running Bundler
-
-Once a manifest file has been created, the only thing that needs to be done
-is to run the `gem bundle` command anywhere in your application. The script
-will load the manifest file, resolve all the dependencies, download all
-needed gems, and install them into the specified directory.
-
-Every time an update is made to the manifest file, run `gem bundle` again to
-get the changes installed. This will only check the remote sources if your
-currently installed gems do not satisfy the `Gemfile`. If you want to force
-checking for updates on the remote sources, use the `--update` option.
-
-### Remote deploys
-
-When you run `gem bundle`, the following steps occur:
-
-1. Gemfile is read in
-2. The gems specified in the Gemfile are resolved against the gems
-   already in your bundle. If the dependencies resolve, skip to step 5.
-3. If the dependencies in your Gemfile cannot be fully resolved
-   against the gems already in the bundle, the metadata for each
-   source is fetched.
-4. The gems in the Gemfile are resolved against the full list of
-   available gems in all sources, and the resulting gems are downloaded
-5. Each gem that has been downloaded but not yet expanded is expanded
-   into the local directory. This expansion process also installs
-   native gems.
-
-As you can see, if you run gem bundle twice in a row, it will do nothing the
-second time, since the gems obviously resolve against the installed gems,
-and they are all expanded.
-
-This also means that if you run `gem bundle`, and .gitignore the expanded
-copies, leaving only the cached `.gem` files, you can run `gem bundle` again
-on the remote system, and it will only expand out the gems (but not
-resolve or download `.gem` files). This also means that native gems
-will be compiled for the target platform without requiring that the
-`.gem` file itself be downloaded from a remote gem server.
-
-Assuming a Rails app with Bundler's standard setup, add something like
-this to your top-level `.gitignore` to only keep the cache:
-
-    bin/*
-    vendor/gems/*
-    !vendor/gems/cache/
-
-Make sure that you explicitly `git add vendor/gems/cache` before you commit.
-
-### Gems with compile-time options
-
-Some gems require you to pass compile-time options to the gem install command.
-For instance, to install mysql, you might do:
-
-    gem install mysql -- --with-mysql-config=/usr/local/lib/mysql
-
-You can pass these options to the bundler by creating a YAML file containing
-the options in question:
-
-    mysql:
-      mysql-config: /usr/local/lib/mysql
-
-You can then point the bundler at the file:
-
-    gem bundle --build-options build_options.yml
-
-In general, you will want to keep the build options YAML out of version control,
-and provide the appropriate options for the system in question.
-
-### Running your application
-
-The easiest way to run your application is to start it with an executable
-copied to the specified bin directory (by default, simply bin). For example,
-if the application in question is a rack app, start it with `bin/rackup`.
-This will automatically set the gem environment correctly.
-
-Another way to run arbitrary ruby code in context of the bundled gems is to
-run it with the `gem exec` command. For example:
-
-    gem exec ruby my_ruby_script.rb
-
-You can use `gem exec bash` to enter a shell that will run all binaries in
-the current context.
-
-Yet another way is to manually require the environment file first. This is
-located in `[bundle_path]/gems/environment.rb`. For example:
-
-    ruby -r vendor/gems/environment.rb my_ruby_script.rb
-
-### Using Bundler with Rails today
-
-It should be possible to use Bundler with Rails today. Here are the steps
-to follow.
-
-* In your rails app, create a Gemfile and specify the gems that your
-  application depends on. Make sure to specify rails as well:
-
-        gem "rails", "2.1.2"
-        gem "will_paginate"
-
-        # Optionally, you can disable system gems all together and only
-        # use bundled gems.
-        disable_system_gems
-
-* Run `gem bundle`
-
-* You can now use rails if you prepend `gem exec` to every call to `script/*`
-  but that isn't fun.
-
-* At the top of `config/preinitializer.rb`, add the following line:
-
-    require "#{RAILS_ROOT}/vendor/gems/environment"
-
-In theory, this should be enough to get going.
-
-## To require rubygems or not
-
-Ideally, no gem would assume the presence of rubygems at runtime. Rubygems provides
-enough features so that this isn't necessary. However, there are a number of gems
-that require specific rubygems features.
-
-If the `disable_rubygems` option is used, Bundler will stub out the most common
-of these features, but it is possible that things will not go as intended quite
-yet. So, if you are brave, try your code without rubygems at runtime.
-
-This is different from the `disable_system_gems` option, which uses the rubygems
-library, but prevents system gems from being loaded; only gems that are bundled
-will be available to your application. This option guarantees that dependencies
-of your application will be available to a remote system.
-
-## Known Issues
-
-* When a gem points to a git repository, the git repository will be cloned
-  every time Bundler does a gem dependency resolve.
-
-## Reporting bugs
-
-Please report all bugs on the github issue tracker for the project located
-at:
-
-    http://github.com/wycats/bundler/issues/