--- !ruby/object:Gem::Specification 
name: sysexits
version: !ruby/object:Gem::Version 
  hash: 19
  prerelease: 
  segments: 
  - 1
  - 1
  - 0
  version: 1.1.0
platform: ruby
authors: 
- Michael Granger
autorequire: 
bindir: bin
cert_chain: 
- |
  -----BEGIN CERTIFICATE-----
  MIIDLDCCAhSgAwIBAgIBADANBgkqhkiG9w0BAQUFADA8MQwwCgYDVQQDDANnZWQx
  FzAVBgoJkiaJk/IsZAEZFgdfYWVyaWVfMRMwEQYKCZImiZPyLGQBGRYDb3JnMB4X
  DTEwMDkxNjE0NDg1MVoXDTExMDkxNjE0NDg1MVowPDEMMAoGA1UEAwwDZ2VkMRcw
  FQYKCZImiZPyLGQBGRYHX2FlcmllXzETMBEGCgmSJomT8ixkARkWA29yZzCCASIw
  DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALy//BFxC1f/cPSnwtJBWoFiFrir
  h7RicI+joq/ocVXQqI4TDWPyF/8tqkvt+rD99X9qs2YeR8CU/YiIpLWrQOYST70J
  vDn7Uvhb2muFVqq6+vobeTkILBEO6pionWDG8jSbo3qKm1RjKJDwg9p4wNKhPuu8
  KGue/BFb67KflqyApPmPeb3Vdd9clspzqeFqp7cUBMEpFS6LWxy4Gk+qvFFJBJLB
  BUHE/LZVJMVzfpC5Uq+QmY7B+FH/QqNndn3tOHgsPadLTNimuB1sCuL1a4z3Pepd
  TeLBEFmEao5Dk3K/Q8o8vlbIB/jBDTUx6Djbgxw77909x6gI9doU4LD5XMcCAwEA
  AaM5MDcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0OBBYEFJeoGkOr9l4B
  +saMkW/ZXT4UeSvVMA0GCSqGSIb3DQEBBQUAA4IBAQBG2KObvYI2eHyyBUJSJ3jN
  vEnU3d60znAXbrSd2qb3r1lY1EPDD3bcy0MggCfGdg3Xu54z21oqyIdk8uGtWBPL
  HIa9EgfFGSUEgvcIvaYqiN4jTUtidfEFw+Ltjs8AP9gWgSIYS6Gr38V0WGFFNzIH
  aOD2wmu9oo/RffW4hS/8GuvfMzcw7CQ355wFR4KB/nyze+EsZ1Y5DerCAagMVuDQ
  U0BLmWDFzPGGWlPeQCrYHCr+AcJz+NRnaHCKLZdSKj/RHuTOt+gblRex8FAh8NeA
  cmlhXe46pZNJgWKbxZah85jIjx95hR8vOI+NAM5iH9kOqK13DrxacTKPhqj5PjwF
  -----END CERTIFICATE-----

date: 2012-09-18 00:00:00 Z
dependencies: 
- !ruby/object:Gem::Dependency 
  name: hoe-mercurial
  prerelease: false
  requirement: &id001 !ruby/object:Gem::Requirement 
    none: false
    requirements: 
    - - ~>
      - !ruby/object:Gem::Version 
        hash: 7
        segments: 
        - 1
        - 4
        - 0
        version: 1.4.0
  type: :development
  version_requirements: *id001
- !ruby/object:Gem::Dependency 
  name: hoe-highline
  prerelease: false
  requirement: &id002 !ruby/object:Gem::Requirement 
    none: false
    requirements: 
    - - ~>
      - !ruby/object:Gem::Version 
        hash: 29
        segments: 
        - 0
        - 0
        - 1
        version: 0.0.1
  type: :development
  version_requirements: *id002
- !ruby/object:Gem::Dependency 
  name: rdoc
  prerelease: false
  requirement: &id003 !ruby/object:Gem::Requirement 
    none: false
    requirements: 
    - - ~>
      - !ruby/object:Gem::Version 
        hash: 19
        segments: 
        - 3
        - 10
        version: "3.10"
  type: :development
  version_requirements: *id003
- !ruby/object:Gem::Dependency 
  name: rspec
  prerelease: false
  requirement: &id004 !ruby/object:Gem::Requirement 
    none: false
    requirements: 
    - - ~>
      - !ruby/object:Gem::Version 
        hash: 21
        segments: 
        - 2
        - 11
        version: "2.11"
  type: :development
  version_requirements: *id004
- !ruby/object:Gem::Dependency 
  name: simplecov
  prerelease: false
  requirement: &id005 !ruby/object:Gem::Requirement 
    none: false
    requirements: 
    - - ~>
      - !ruby/object:Gem::Version 
        hash: 7
        segments: 
        - 0
        - 6
        version: "0.6"
  type: :development
  version_requirements: *id005
- !ruby/object:Gem::Dependency 
  name: hoe
  prerelease: false
  requirement: &id006 !ruby/object:Gem::Requirement 
    none: false
    requirements: 
    - - ~>
      - !ruby/object:Gem::Version 
        hash: 7
        segments: 
        - 3
        - 0
        version: "3.0"
  type: :development
  version_requirements: *id006
description: "Have you ever wanted to call <code>exit()</code> with an error condition, but\n\
  weren't sure what exit status to use? No? Maybe it's just me, then.\n\n\
  Anyway, I was reading manpages late one evening before retiring to bed in my\n\
  palatial estate in rural Oregon, and I stumbled across\n\
  <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for\n\
  Ruby! Well, for the other 2 people that actually care about\n\
  <code>style(9)</code> as it applies to Ruby code, now there is one!\n\n\
  Sysexits is a *completely* *awesome* collection of human-readable constants for\n\
  the standard (BSDish) exit codes, used as arguments to +exit+ to\n\
  indicate a specific error condition to the parent process.\n\n\
  It's so fantastically fabulous that you'll want to fork it right away to avoid\n\
  being thought of as that guy that's still using Webrick for his blog. I mean,\n\
  <code>exit(1)</code> is so pass\xC3\xA9! This is like the 14-point font of Systems\n\
  Programming.\n\n\
  Like the C header file from which this was derived (I mean forked, naturally),\n\
  error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool\n\
  than plain old +64+) to reduce the possibility of clashing with other exit\n\
  statuses that other programs may already return.\n\n\
  The codes are available in two forms: as constants which can be imported into\n\
  your own namespace via <code>include Sysexits</code>, or as\n\
  <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the\n\
  constant names.\n\n\
  Allow me to demonstrate. First, the old way:\n\n    exit( 69 )\n\n\
  Whaaa...? Is that a euphemism? What's going on? See how unattractive and...\n\
  well, 1970 that is? We're not changing vaccuum tubes here, people, we're\n\
  <em>building a totally-awesome future in the Cloud\xE2\x84\xA2!</em>\n\n    include Sysexits\n    exit EX_UNAVAILABLE\n\n\
  Okay, at least this is readable to people who have used <code>fork()</code>\n\
  more than twice, but you could do so much better!\n\n    include Sysexits\n    exit :unavailable\n\n\
  Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in\n\
  which variable++ is possible! Well, okay, it's not quite that cool. But it\n\
  does look more Rubyish. And no monkeys were patched in the filming of this\n\
  episode! All the simpletons still exiting with icky _numbers_ can still\n\
  continue blithely along, none the wiser."
email: 
- ged@FaerieMUD.org
executables: []

extensions: []

extra_rdoc_files: 
- History.rdoc
- Manifest.txt
- README.rdoc
files: 
- ChangeLog
- History.rdoc
- LICENSE
- Manifest.txt
- README.rdoc
- Rakefile
- lib/sysexits.rb
- spec/sysexits_spec.rb
- .gemtest
homepage: https://bitbucket.org/ged/sysexits
licenses: 
- BSD
post_install_message: "\n\
  Get ready to be amazed. I'll bet you can't wait to Exit Like \n\
  a Pro\xC2\xAE!\n\n\
  Well, if you want, you can do it right from the command-line! Check \n\
  this out:\n\n  ruby -rubygems -e \\\n    'require \"sysexits\"; include Sysexits; exit :software_error' \\\n    || echo $?\n\n\
  I know, I know: so awesome right? Okay, I'll let you bask in the\n\
  warn glow of superior systems-programming now.\n\n"
rdoc_options: 
- -f
- fivefish
- -t
- Sysexits
require_paths: 
- lib
required_ruby_version: !ruby/object:Gem::Requirement 
  none: false
  requirements: 
  - - ">="
    - !ruby/object:Gem::Version 
      hash: 57
      segments: 
      - 1
      - 8
      - 7
      version: 1.8.7
required_rubygems_version: !ruby/object:Gem::Requirement 
  none: false
  requirements: 
  - - ">="
    - !ruby/object:Gem::Version 
      hash: 3
      segments: 
      - 0
      version: "0"
requirements: []

rubyforge_project: sysexits
rubygems_version: 1.8.24
signing_key: 
specification_version: 3
summary: Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then
test_files: []