bio-commandeer 0.1.1 → 0.1.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (5) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile +1 -1
  3. data/README.md +6 -1
  4. data/VERSION +1 -1
  5. metadata +3 -3
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: c544cb54f4692c602acb4c3b7b4ed6b433abe8d1
4
- data.tar.gz: 4f46eee196608fa65fb2a3d8bfcf246615ddea1a
3
+ metadata.gz: 5d1436e7c7b10bdcdf1a2924bdf1e2449a6f69da
4
+ data.tar.gz: fefffaf42425620e2eaa40a1a03a1b4d54430a5f
5
5
  SHA512:
6
- metadata.gz: 5e66f6b0c25450feb81a939758ef9fb761f6deba44ecf03f7e23aee62f26fdaf0f735a9ac084cc6a2dd309ef3b2c56238a9d58bd17f7c6315cb318822cae7c5e
7
- data.tar.gz: 013a8046ced4623cb65e86afd180898a9f43d2c275f83cdafe54279033e096a2c73263602286d6dca0325774ba8b628d1baccca14f5b56c2388754a0575964a6
6
+ metadata.gz: 476d9922c20d8975144843baa7f8e6ca1cc4bc6fb64ebbaf20a70dcfe7f6f74d3f419e99e16dd9ffecee6a81bbea54ba6533f5ea32fbe2ec796565be4a1f1f95
7
+ data.tar.gz: 286e80621fc7112211486b89301d7c0b3343e05068b453f1e411c6c1b1bfd5144e70ccc919d29742fa41435b7cb89743a8648e5931a084ba5179801cd6d8af2b
data/Gemfile CHANGED
@@ -9,7 +9,7 @@ gem 'systemu', '~>2.6'
9
9
  # Include everything needed to run rake, tests, features, etc.
10
10
  group :development do
11
11
  gem "rspec", "~> 3.2"
12
- gem "rdoc", "~> 3.12"
12
+ gem "rdoc", "~>4.2"
13
13
  gem "jeweler", "~> 2.0"
14
14
  gem "bundler", "~> 1.3"
15
15
  end
data/README.md CHANGED
@@ -9,6 +9,7 @@ require 'bio-commandeer'
9
9
  Bio::Commandeer.run 'echo 5' #=> "5\n"
10
10
  ```
11
11
  The real advantage of bio-commandeer is that when something goes wrong, it tells you; you don't have go looking for the error. Take for instance this simple script:
12
+
12
13
  ```ruby
13
14
  #!/usr/bin/env ruby
14
15
  require 'bio-commandeer'
@@ -16,6 +17,7 @@ print Bio::Commandeer.run('echo 5')
16
17
  print Bio::Commandeer.run('cat /not_a_file')
17
18
  ```
18
19
  The output is:
20
+
19
21
  ```sh
20
22
  5
21
23
  <snip>/lib/bio-commandeer/commandeer.rb:32:in `run': Command returned non-zero exit status (1), likely indicating failure. Command run was cat /not_a_file and the STDERR was: (Bio::CommandFailedException)
@@ -30,17 +32,20 @@ Note: this software is under active development! Currently it is perhaps overly
30
32
 
31
33
  ## Logging
32
34
  Commands run are logged with level info, if requested:
35
+
33
36
  ```ruby
34
37
  require 'bio-commandeer'
35
38
  Bio::Log::CLI.logger("stderr"); Bio::Log::CLI.trace("info");
36
39
  puts Bio::Commandeer.run 'echo 5', :log=>true
37
40
  ```
38
41
  On stderr this gives
42
+
39
43
  ```
40
44
  INFO bio-commandeer: Running command: echo 5
41
45
  INFO bio-commandeer: Command finished with exitstatus 0
42
46
  ```
43
47
  Or a logging can be given directly, so long as it has an `info` method:
48
+
44
49
  ```ruby
45
50
  Bio::Commandeer.run 'echo 5', :log=>my_logger
46
51
  ```
@@ -58,5 +63,5 @@ This Biogem is published at (http://biogems.info/index.html#bio-commandeer)
58
63
 
59
64
  ## Copyright
60
65
 
61
- Copyright (c) 2014 Ben J. Woodcroft. See LICENSE.txt for further details.
66
+ Copyright (c) 2014-2015 Ben J. Woodcroft. See LICENSE.txt for further details.
62
67
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.1.1
1
+ 0.1.2
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: bio-commandeer
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.1
4
+ version: 0.1.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Ben J. Woodcroft
@@ -58,14 +58,14 @@ dependencies:
58
58
  requirements:
59
59
  - - "~>"
60
60
  - !ruby/object:Gem::Version
61
- version: '3.12'
61
+ version: '4.2'
62
62
  type: :development
63
63
  prerelease: false
64
64
  version_requirements: !ruby/object:Gem::Requirement
65
65
  requirements:
66
66
  - - "~>"
67
67
  - !ruby/object:Gem::Version
68
- version: '3.12'
68
+ version: '4.2'
69
69
  - !ruby/object:Gem::Dependency
70
70
  name: jeweler
71
71
  requirement: !ruby/object:Gem::Requirement