quintus-example-gem 0.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. data/COPYING.rdoc +0 -0
  2. data/README.rdoc +37 -0
  3. data/bin/example +4 -0
  4. data/lib/example.rb +13 -0
  5. metadata +71 -0
File without changes
@@ -0,0 +1,37 @@
1
+ = Example
2
+
3
+ This is the README file for the example gem.
4
+
5
+ == Installation
6
+
7
+ # gem install example_gem
8
+
9
+ == Usage
10
+
11
+ require "example"
12
+ Example.new.hi #=> Some example message on the console
13
+
14
+ == License
15
+
16
+ Never forget to add a license to your code, otherwise people will
17
+ either start picking around you or not even use your code at all. If
18
+ unsure, refer to these guidelines:
19
+
20
+ 1. If you want to enforce any application using your code to be
21
+ open-source’d, use the GNU GPLv3. This is a good choice for end-user
22
+ applications, but not for libraries as it prohibits most comercial
23
+ use.
24
+
25
+ 2. If you want to ensure that closed-source (read: most comercial)
26
+ projects can use your library, but at the same time want to ensure
27
+ that they are forced to publish *your* code’s part in that project,
28
+ use the GNU LGPLv3.
29
+
30
+ 3. If you want to let anyone do anything with your library, just
31
+ ensuring they mention your name, use the 2-Clause-BSDL. This is what
32
+ Ruby itself uses.
33
+
34
+ 4. Otherwise... Well, no otherwise. You should consider all three
35
+ points above, and if they don’t serve you, refer to
36
+ http://opensource.org/licenses/index.html for a list of OSI-approved
37
+ licenses and pick one that servers you better.
@@ -0,0 +1,4 @@
1
+ #!/usr/bin/env ruby
2
+ require_relative "../lib/example"
3
+
4
+ Example.new.hi
@@ -0,0 +1,13 @@
1
+ require "paint"
2
+
3
+ #Example class. It's sole purpose is to demonstrate how to
4
+ #build a RubyGem.
5
+ class Example
6
+
7
+ #Example method. Takes no parameters and returns +nil+.
8
+ #Outputs a nice message on the console.
9
+ def hi
10
+ puts Paint["This is an example RubyGem.", :green]
11
+ end
12
+
13
+ end
metadata ADDED
@@ -0,0 +1,71 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: quintus-example-gem
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.0.1
5
+ prerelease:
6
+ platform: ruby
7
+ authors:
8
+ - Marvin Gülker
9
+ autorequire:
10
+ bindir: bin
11
+ cert_chain: []
12
+ date: 2012-07-18 00:00:00.000000000 Z
13
+ dependencies:
14
+ - !ruby/object:Gem::Dependency
15
+ name: paint
16
+ requirement: !ruby/object:Gem::Requirement
17
+ none: false
18
+ requirements:
19
+ - - ! '>='
20
+ - !ruby/object:Gem::Version
21
+ version: '0'
22
+ type: :runtime
23
+ prerelease: false
24
+ version_requirements: !ruby/object:Gem::Requirement
25
+ none: false
26
+ requirements:
27
+ - - ! '>='
28
+ - !ruby/object:Gem::Version
29
+ version: '0'
30
+ description: ! 'This is an example gem demonstrating how to create RubyGems.
31
+
32
+ '
33
+ email: quintus@quintilianus.eu
34
+ executables:
35
+ - example
36
+ extensions: []
37
+ extra_rdoc_files:
38
+ - README.rdoc
39
+ - COPYING.rdoc
40
+ files:
41
+ - lib/example.rb
42
+ - bin/example
43
+ - README.rdoc
44
+ - COPYING.rdoc
45
+ homepage: http://example.org
46
+ licenses: []
47
+ post_install_message:
48
+ rdoc_options:
49
+ - -m
50
+ - README.rdoc
51
+ require_paths:
52
+ - lib
53
+ required_ruby_version: !ruby/object:Gem::Requirement
54
+ none: false
55
+ requirements:
56
+ - - ! '>='
57
+ - !ruby/object:Gem::Version
58
+ version: '1.9'
59
+ required_rubygems_version: !ruby/object:Gem::Requirement
60
+ none: false
61
+ requirements:
62
+ - - ! '>='
63
+ - !ruby/object:Gem::Version
64
+ version: '0'
65
+ requirements: []
66
+ rubyforge_project:
67
+ rubygems_version: 1.8.24
68
+ signing_key:
69
+ specification_version: 3
70
+ summary: An example gem
71
+ test_files: []