stickler 0.1.0 → 0.1.1

data/HISTORY.rdoc

@@ -0,0 +1,9 @@
+= stickler Changelog
+
+=== Version 0.1.1
+* 1 minor bugfix
+  * remove unnecessary require 'progressbar' 
+
+=== Version 0.1.0
+* {Managing a Gem Repository with Stickler}[http://copiousfreetime.org/articles/2008/10/09/managing-a-gem-repository-with-stickler.html]
+* Initial public release

data/{README → README.rdoc}

@@ -3,10 +3,11 @@
 * Homepage[http://copiousfreetime.rubyforge.org/stickler/]
 * {Rubyforge Project}[http://rubyforge.org/projects/copiousfreetime/]
 * email jeremy at hinegardner dot org 
+* {Managing a Gem Repository with Stickler}[http://copiousfreetime.org/articles/2008/10/09/managing-a-gem-repository-with-stickler.html]
 
 == DESCRIPTION
 
-Stickler is a tool to organize and maintain an internal gem distribution.
+Stickler is a tool to organize and maintain an internal gem repository.
 
 At times it is useful to have complete control over the availability of the gems
 for you testing, staging and production environments.  In these cases you
@@ -17,6 +18,7 @@ Configure stickler with the the names and versions of the gems you require for
 your deployment and it will organize and setup everything that is necessary for
 a standard web server to function as your internal gem distribution server.
 
+
 == INSTALLATION
 
 Install as a gem:

data/lib/stickler/source.rb

@@ -1,6 +1,5 @@
 require 'uri'
 require 'base64'
-require 'progressbar'
 require 'zlib'
 
 module Stickler

data/lib/stickler/version.rb

@@ -12,7 +12,7 @@ module Stickler
 
     MAJOR = 0
     MINOR = 1
-    BUILD = 0
+    BUILD = 1
 
     def self.to_ary
       [ MAJOR, MINOR, BUILD ]

data/tasks/config.rb

@@ -12,11 +12,11 @@ Configuration.for('project') {
   author        "Jeremy Hinegardner"
   email         "jeremy at copiousfreetime dot org"
   homepage      "http://copiousfreetime.rubyforge.org/stickler"
-  description   Utils.section_of("README", "description")
+  description   Utils.section_of("README.rdoc", "description")
   summary       description.split(".").first
-  history       "HISTORY"
+  history       "HISTORY.rdoc"
   license       FileList["LICENSE", "COPYING"]
-  readme        "README"
+  readme        "README.rdoc"
 }
 
 #-----------------------------------------------------------------------

data/tasks/distribution.rake

@@ -34,5 +34,12 @@ if pkg_config = Configuration.for_if_exist?("packaging") then
     desc "reinstall gem"
     task :reinstall => [:uninstall, :repackage, :install]
 
+    desc "distribute copiously"
+    task :copious => [:package] do
+      Rake::SshFilePublisher.new('jeremy@copiousfreetime.org',
+                               '/var/www/vhosts/www.copiousfreetime.org/htdocs/gems/gems',
+                               'pkg',"#{Stickler::GEM_SPEC.full_name}.gem").upload
+      sh "ssh jeremy@copiousfreetime.org rake -f /var/www/vhosts/www.copiousfreetime.org/htdocs/gems/Rakefile"
+    end  
  end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: stickler
 version: !ruby/object:Gem::Version 
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors: 
 - Jeremy Hinegardner
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2008-10-09 00:00:00 -06:00
+date: 2008-10-12 00:00:00 -06:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -72,15 +72,15 @@ dependencies:
       - !ruby/object:Gem::Version 
         version: "0.0"
     version: 
-description: Stickler is a tool to organize and maintain an internal gem distribution.  At times it is useful to have complete control over the availability of the gems for you testing, staging and production environments.  In these cases you probably do not want to accidentally type 'gem update' and get a new untested version of a gem installed on your machines.  This is where Stickler helps.  Configure stickler with the the names and versions of the gems you require for your deployment and it will organize and setup everything that is necessary for a standard web server to function as your internal gem distribution server.
+description: Stickler is a tool to organize and maintain an internal gem repository.  At times it is useful to have complete control over the availability of the gems for you testing, staging and production environments.  In these cases you probably do not want to accidentally type 'gem update' and get a new untested version of a gem installed on your machines.  This is where Stickler helps.  Configure stickler with the the names and versions of the gems you require for your deployment and it will organize and setup everything that is necessary for a standard web server to function as your internal gem distribution server.
 email: jeremy at copiousfreetime dot org
 executables: 
 - stickler
 extensions: []
 
 extra_rdoc_files: 
-- README
-- HISTORY
+- README.rdoc
+- HISTORY.rdoc
 - LICENSE
 - COPYING
 - lib/stickler/cli.rb
@@ -111,8 +111,8 @@ files:
 - spec/spec_helper.rb
 - spec/version_spec.rb
 - data/stickler.yml
-- README
-- HISTORY
+- README.rdoc
+- HISTORY.rdoc
 - LICENSE
 - COPYING
 - tasks/announce.rake
@@ -130,7 +130,7 @@ rdoc_options:
 - --line-numbers
 - --inline-source
 - --main
-- README
+- README.rdoc
 require_paths: 
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement 
@@ -151,6 +151,6 @@ rubyforge_project: copiousfreetime
 rubygems_version: 1.2.0
 signing_key: 
 specification_version: 2
-summary: Stickler is a tool to organize and maintain an internal gem distribution
+summary: Stickler is a tool to organize and maintain an internal gem repository
 test_files: []
 

data/HISTORY

@@ -1,4 +0,0 @@
-= stickler Changelog
-=== Version 0.0.1
-
-* Initial public release