Narnach-gems 0.1.4 → 0.1.5

data/README.rdoc

@@ -5,6 +5,10 @@ Rails code would not get into dependency issues.
 
 == Recent changes
 
+=== Version 0.1.5
+Gem import accepts 'current' as a special file name, which will use the output
+of 'gem list' instead of a real file. This makes it easy to store the current gem configuration.
+
 === Version 0.1.4
 It is now possible to add a list of gems to an existing project.
 Changed internal storage format of ~/.gems.yml, which is auto-converted on use.
@@ -40,25 +44,30 @@ From the project root, use rake to install:
 This will build the gem and install it for you.
 
 == Usage
-Output if 'gems help':
+Output if 'gems help', with some changes to make them legible in RDoc:
   Syntax:
-    gems <action> <arguments>
+    gems 'action' 'arguments'
 
   Actions and arguments:
-    install <name>
-      Install all gems in project <name>.
-    uninstall <name>
-      Uninstall all gems in project <name>.
-    list <name>
-      List all gems in project <name>.
-    import <name> <file>
-      Import all gems in <file> into project <name>.
+    install 'name'
+      Install all gems in project 'name'.
+    uninstall 'name'
+      Uninstall all gems in project 'name'.
+    list 'name'
+      List all gems in project 'name'.
+    import 'name' 'file'
+      Import all gems in 'file' into project 'name'.
       This will overwrite the gems currently in this project.
-    export <name> <file>
-      Export all gems in project <name> to <file>.
+      The special file 'current' will use the output of `gems list` instead of a file.
+    export 'name' 'file'
+      Export all gems in project 'name' to 'file'.
       The file will be overwritten and can be parsed by the import action.
+    add 'name' 'file'
+      Add the gems 'file' to project 'name'.
     projects
       List all stored project names.
+    configure 'name' 'gem' [option1 option2 option3]
+      Configure a specific gem inside a project to use specific options when installing.
 
 == Examples
 To store your current gems as project 'dev', do the following:
@@ -71,7 +80,7 @@ To export project 'dev' to the file 'gems.dev', do the following:
   gems export dev gems.dev
 
 == About
-Author:: Wes 'Narnach' Oldenbeuving (narnach@gmail.com)
-Website:: http://www.github.com/Narnach/gems
+Author:: Wes 'Narnach' Oldenbeuving (http://github.com/Narnach)
+Website:: http://github.com/Narnach/gems
 Copyright:: Copyright (c) 2008 Wes Oldenbeuving
 License:: MIT license. See MIT-LICENSE (in the gem directory) for license details.

data/bin/gems

@@ -50,6 +50,7 @@ Actions and arguments:
   import <name> <file>
     Import all gems in <file> into project <name>.
     This will overwrite the gems currently in this project.
+    The special file 'current' will use the output of `gems list` instead of a file.
   export <name> <file>
     Export all gems in project <name> to <file>.
     The file will be overwritten and can be parsed by the import action.

data/gems.gemspec

@@ -3,7 +3,7 @@ Gem::Specification.new do |s|
   s.name         = 'gems'
   s.summary      = "Gems is a simple tool to manage sets of RubyGems."
   s.description  = "Gems is a simple tool to manage sets of RubyGems. It can be used to install and uninstall large numbers of gems."
-  s.version      = '0.1.4'
+  s.version      = '0.1.5'
   s.date         = '2008-08-19'
   s.platform     = Gem::Platform::RUBY
   s.authors      = ["Wes Oldenbeuving"]

data/lib/gems_parser.rb

@@ -34,7 +34,11 @@ class GemsParser
   end
 
   def read_file
-    raise 'File does not exist: "%s"' % file unless File.exist?(file)
-    File.read(file)
+    if file == 'current'
+      return `gem list`
+    else
+      raise 'File does not exist: "%s"' % file unless File.exist?(file)
+      return File.read(file)
+    end
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: Narnach-gems
 version: !ruby/object:Gem::Version 
-  version: 0.1.4
+  version: 0.1.5
 platform: ruby
 authors: 
 - Wes Oldenbeuving