detroit 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (51) hide show
  1. data/.ruby +45 -0
  2. data/COPYING.rdoc +19 -0
  3. data/EXAMPLE.md +188 -0
  4. data/GPL3.txt +675 -0
  5. data/HISTORY.rdoc +14 -0
  6. data/README.rdoc +139 -0
  7. data/bin/detroit +9 -0
  8. data/lib/detroit.rb +67 -0
  9. data/lib/detroit.yml +45 -0
  10. data/lib/detroit/application.rb +427 -0
  11. data/lib/detroit/assembly.rb +80 -0
  12. data/lib/detroit/config.rb +197 -0
  13. data/lib/detroit/control.rb +124 -0
  14. data/lib/detroit/core_ext.rb +139 -0
  15. data/lib/detroit/custom.rb +65 -0
  16. data/lib/detroit/dsl.rb +55 -0
  17. data/lib/detroit/schedule.rb +187 -0
  18. data/lib/detroit/service.rb +188 -0
  19. data/lib/detroit/standard_assembly.rb +52 -0
  20. data/lib/detroit/tool.rb +216 -0
  21. data/lib/detroit/tool/core_ext.rb +3 -0
  22. data/lib/detroit/tool/core_ext/facets.rb +11 -0
  23. data/lib/detroit/tool/core_ext/filetest.rb +29 -0
  24. data/lib/detroit/tool/core_ext/shell_extensions.rb +7 -0
  25. data/lib/detroit/tool/core_ext/to_actual_filename.rb +19 -0
  26. data/lib/detroit/tool/core_ext/to_console.rb +97 -0
  27. data/lib/detroit/tool/core_ext/to_list.rb +29 -0
  28. data/lib/detroit/tool/core_ext/to_yamlfrag.rb +9 -0
  29. data/lib/detroit/tool/core_ext/unfold_paragraphs.rb +27 -0
  30. data/lib/detroit/tool/email_utils.rb +288 -0
  31. data/lib/detroit/tool/project_utils.rb +41 -0
  32. data/lib/detroit/tool/shell_utils.rb +235 -0
  33. data/qed/01_schedule/02_initialize.md +57 -0
  34. data/qed/99_plugins/rdoc/rdoc-plugin.rdoc +22 -0
  35. data/qed/99_plugins/rdoc/sample/Syckfile +6 -0
  36. data/qed/99_plugins/rdoc/sample/lib/sandbox/.xxx +1 -0
  37. data/qed/99_plugins/rdoc/sample/lib/sandbox/hello.rb +5 -0
  38. data/qed/99_plugins/rdoc/sample/lib/sandbox/xxx.rb +6 -0
  39. data/qed/99_plugins/rdoc/sample/lib/xxx/bye.rb +4 -0
  40. data/qed/99_plugins/rdoc/sample/meta/name +1 -0
  41. data/qed/99_plugins/rdoc/sample/meta/version +1 -0
  42. data/qed/samples/example_project/.ruby +0 -0
  43. data/qed/samples/example_project/Schedule +9 -0
  44. data/qed/samples/example_project/lib/foo/.xxx +1 -0
  45. data/qed/samples/example_project/lib/foo/hello.rb +7 -0
  46. data/qed/samples/example_project/lib/foo/xxx.rb +6 -0
  47. data/qed/samples/example_project/lib/foo/xxx/bye.rb +4 -0
  48. data/qed/samples/example_project/meta/name +1 -0
  49. data/qed/samples/example_project/meta/version +1 -0
  50. data/qed/samples/example_schedule.rb +57 -0
  51. metadata +139 -0
data/.ruby ADDED
@@ -0,0 +1,45 @@
1
+ ---
2
+ name: detroit
3
+ version: 0.1.0
4
+ title: Detroit
5
+ summary: Software Production Mangement
6
+ description: Detroit is an advanced lifecycle build system. With Detroit, build tasks are user defined service instances tied to stops along a track. Whenever the detroit console command is run, a track is followed from beginning to designated destination.
7
+ loadpath:
8
+ - lib
9
+ manifest: Manifest
10
+ requires:
11
+ - name: facets
12
+ version: 0+
13
+ group: []
14
+
15
+ - name: pom
16
+ version: 0+
17
+ group: []
18
+
19
+ - name: qed
20
+ version: 0+
21
+ group:
22
+ - test
23
+ conflicts: []
24
+
25
+ replaces: []
26
+
27
+ engine_check: []
28
+
29
+ organization: Rubyworks
30
+ contact: Trans <transfire@gmail.com>
31
+ created: 2007-10-10
32
+ copyright: Copyright (c) 2007 Thomas Sawyer
33
+ licenses:
34
+ - GPL3
35
+ authors:
36
+ - Thomas Sawyer
37
+ maintainers: []
38
+
39
+ resources:
40
+ home: http://rubyworks.github.com/detroit
41
+ code: http://github.com/rubyworks/detroit
42
+ mail: http://groups.google.com/rubyworks-mailinglist
43
+ repositories:
44
+ public: http://github.com/proutils/detroit.git
45
+ spec_version: 1.0.0
@@ -0,0 +1,19 @@
1
+ = COPYRIGHT NOTICES
2
+
3
+ == Detroit
4
+
5
+ Copyright (c) 2011 Thomas Sawyer
6
+
7
+ This program is free software: you can redistribute it and/or modify
8
+ it under the terms of the GNU General Public License as published by
9
+ the Free Software Foundation, either version 3 of the License, or
10
+ (at your option) any later version.
11
+
12
+ This program is distributed in the hope that it will be useful,
13
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
14
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
15
+ GNU General Public License for more details.
16
+
17
+ You should have received a copy of the GNU General Public License
18
+ along with this program. If not, see <http://www.gnu.org/licenses/>.
19
+
@@ -0,0 +1,188 @@
1
+ # Detroit
2
+
3
+ Detroit's main configuration file is called a *Pitfile*. Pitfiles define the
4
+ <i>service instances</i> that a project will utilize.
5
+
6
+ Pitfiles can be written in a few different formats thanks to the flexibility
7
+ of Ruby. All formats are equivalent. Which format you use is strictly a regard
8
+ of your personal preference.
9
+
10
+ ## Ruby-based Detroit
11
+
12
+ ### Traditional Format
13
+
14
+ Traditionally a Ruby-based Detroit is dominated by calls to the `service` method
15
+ with an optional service instance name and a setter block.
16
+
17
+ ```ruby
18
+ service :myself do |s|
19
+ s.service = :Announce
20
+ s.mailto = "transfire@gmail.com"
21
+ s.active = true
22
+ end
23
+
24
+ service :rdoc do |r|
25
+ r.include = [ 'lib', '[A-Z]*' ]
26
+ r.exclude = [ 'Schedule' ]
27
+ end
28
+ ```
29
+
30
+ If no `service` setting is given, it is assumed to be same as the service instance name.
31
+ In the above example `rdoc` is taken to be both the service desired and the name of
32
+ this particular instance.
33
+
34
+ A few years ago, Sinatra came along and popularized the use of the `#set` method. A simple addition
35
+ to the the Detroit parser now allows for the slightly cleaner notation:
36
+
37
+ ```ruby
38
+ service :myself do
39
+ set :service, :Announce
40
+ set :mailto, "transfire@gmail.com"
41
+ set :priority, -1
42
+ set :active, true
43
+ end
44
+
45
+ service :rdoc do
46
+ set :include, [ 'lib', '[A-Z]*' ]
47
+ set :exclude, [ 'Schedule' ]
48
+ end
49
+ ```
50
+
51
+ The `#set` method also allows for nested set blocks to define hash values.
52
+
53
+ ```ruby
54
+ service :rubyforge do
55
+ set :sitemap do
56
+ set :site, name
57
+ end
58
+ set :active, false
59
+ end
60
+ ```
61
+
62
+ The setting `active` defaults to `true` if not given, so is not strictly
63
+ needed in the above examples, but it is convenient to have in case you
64
+ ever need to deactivate a service temporarily --more convenient than
65
+ remarking out a whole section.
66
+
67
+ Almost all options have standard defaults so it is often possible for a service
68
+ definition to be written as simply as:
69
+
70
+ ```ruby
71
+ service :rdoc
72
+ ```
73
+
74
+ ### Modern Notation
75
+
76
+ Thanks to some straight-forward meta-programming, a Ruby-based Detroit can
77
+ be written in a more concisely notation by using the name of the service class as a
78
+ method. This can be followed by a settings block, as with the above examples,
79
+ or passed a <i>settings hash</i>. In which case a Detroit can look like this:
80
+
81
+ ```ruby
82
+ Announce :mailto => "ruby-talk@ruby-lang.org",
83
+ :active => true
84
+
85
+ Announce :myself,
86
+ :mailto => "transfire@gmail.com",
87
+ :priority => -1
88
+ :active => true
89
+
90
+ Gem :types => ['gem'],
91
+ :spec => false,
92
+ :active => true
93
+
94
+ DNote :priority => -1,
95
+ :active => true
96
+
97
+ RI :exclude => [],
98
+ :active => true
99
+
100
+ RDoc :include => [ 'lib', '[A-Z]*' ],
101
+ :exclude => [ 'Schedule' ]
102
+
103
+ Testrb :active => true
104
+
105
+ Rubyforge :sitemap => {
106
+ :site => name
107
+ }
108
+ :active => false
109
+ ```
110
+
111
+ This format is convenient in that it reduced the amount of extraneous syntax
112
+ need to define service instances. With Ruby 1.9 it can be even more conisce
113
+ using the new Hash syntax.
114
+
115
+ ```ruby
116
+ Announce :myself,
117
+ mailto: "transfire@gmail.com",
118
+ priority: -1
119
+ active: true
120
+ ```
121
+
122
+ But you might want to hold off on that a couple of years until Ruby 1.8 is pretty much
123
+ shot and buried ;)
124
+
125
+ ## YAML-based Detroit
126
+
127
+ We have saved the most concise notation for last. The YAML format is
128
+ essentially the same as the traditional Ruby format except that
129
+ the main key provides the service instance name and the service is a
130
+ setting which defaults to the name. Also, notice the start document indicator
131
+ (<code>---</code>). The indicator is NECESSARY for the Detroit to be
132
+ recognized as YAML, rather than Ruby.
133
+
134
+ ```yaml
135
+ --- !detroit
136
+
137
+ announce:
138
+ mailto: "transfire@gmail.com"
139
+ active: true
140
+
141
+ myself:
142
+ service: Announce
143
+ mailto: "transfire@gmail.com"
144
+ active: true
145
+
146
+ gem:
147
+ types: ['gem']
148
+ autospec: false
149
+ active: true
150
+
151
+ dnote:
152
+ priority: -1
153
+ active: true
154
+
155
+ rdoc:
156
+ include: [ lib, '[A-Z]*' ]
157
+ exclude: [ Schedule ]
158
+
159
+ ri:
160
+ exclude: []
161
+ active: true
162
+
163
+ stats:
164
+ priority: -1
165
+ active: true
166
+
167
+ testrb:
168
+ active: true
169
+
170
+ rubyforge:
171
+ service: forge
172
+ sitemap:
173
+ site: <% name %>
174
+ active: false
175
+ ```
176
+
177
+ As we can see in the last entry, the YAML format also supports ERB and provides
178
+ access to project metadata via the ERB's binding.
179
+
180
+ With the Ruby format it is easy enough to load external Detroit plugins using
181
+ standard `require` and `load` methods. Since the YAML format supports ERB
182
+ it can be used to achieve the same effect.
183
+
184
+ ```ruby
185
+ --- !detroit
186
+ <% require 'some/detroit/plugin' %>
187
+ ```
188
+
@@ -0,0 +1,675 @@
1
+
2
+ GNU GENERAL PUBLIC LICENSE
3
+ Version 3, 29 June 2007
4
+
5
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
6
+ Everyone is permitted to copy and distribute verbatim copies
7
+ of this license document, but changing it is not allowed.
8
+
9
+ Preamble
10
+
11
+ The GNU General Public License is a free, copyleft license for
12
+ software and other kinds of works.
13
+
14
+ The licenses for most software and other practical works are designed
15
+ to take away your freedom to share and change the works. By contrast,
16
+ the GNU General Public License is intended to guarantee your freedom to
17
+ share and change all versions of a program--to make sure it remains free
18
+ software for all its users. We, the Free Software Foundation, use the
19
+ GNU General Public License for most of our software; it applies also to
20
+ any other work released this way by its authors. You can apply it to
21
+ your programs, too.
22
+
23
+ When we speak of free software, we are referring to freedom, not
24
+ price. Our General Public Licenses are designed to make sure that you
25
+ have the freedom to distribute copies of free software (and charge for
26
+ them if you wish), that you receive source code or can get it if you
27
+ want it, that you can change the software or use pieces of it in new
28
+ free programs, and that you know you can do these things.
29
+
30
+ To protect your rights, we need to prevent others from denying you
31
+ these rights or asking you to surrender the rights. Therefore, you have
32
+ certain responsibilities if you distribute copies of the software, or if
33
+ you modify it: responsibilities to respect the freedom of others.
34
+
35
+ For example, if you distribute copies of such a program, whether
36
+ gratis or for a fee, you must pass on to the recipients the same
37
+ freedoms that you received. You must make sure that they, too, receive
38
+ or can get the source code. And you must show them these terms so they
39
+ know their rights.
40
+
41
+ Developers that use the GNU GPL protect your rights with two steps:
42
+ (1) assert copyright on the software, and (2) offer you this License
43
+ giving you legal permission to copy, distribute and/or modify it.
44
+
45
+ For the developers' and authors' protection, the GPL clearly explains
46
+ that there is no warranty for this free software. For both users' and
47
+ authors' sake, the GPL requires that modified versions be marked as
48
+ changed, so that their problems will not be attributed erroneously to
49
+ authors of previous versions.
50
+
51
+ Some devices are designed to deny users access to install or run
52
+ modified versions of the software inside them, although the manufacturer
53
+ can do so. This is fundamentally incompatible with the aim of
54
+ protecting users' freedom to change the software. The systematic
55
+ pattern of such abuse occurs in the area of products for individuals to
56
+ use, which is precisely where it is most unacceptable. Therefore, we
57
+ have designed this version of the GPL to prohibit the practice for those
58
+ products. If such problems arise substantially in other domains, we
59
+ stand ready to extend this provision to those domains in future versions
60
+ of the GPL, as needed to protect the freedom of users.
61
+
62
+ Finally, every program is threatened constantly by software patents.
63
+ States should not allow patents to restrict development and use of
64
+ software on general-purpose computers, but in those that do, we wish to
65
+ avoid the special danger that patents applied to a free program could
66
+ make it effectively proprietary. To prevent this, the GPL assures that
67
+ patents cannot be used to render the program non-free.
68
+
69
+ The precise terms and conditions for copying, distribution and
70
+ modification follow.
71
+
72
+ TERMS AND CONDITIONS
73
+
74
+ 0. Definitions.
75
+
76
+ "This License" refers to version 3 of the GNU General Public License.
77
+
78
+ "Copyright" also means copyright-like laws that apply to other kinds of
79
+ works, such as semiconductor masks.
80
+
81
+ "The Program" refers to any copyrightable work licensed under this
82
+ License. Each licensee is addressed as "you". "Licensees" and
83
+ "recipients" may be individuals or organizations.
84
+
85
+ To "modify" a work means to copy from or adapt all or part of the work
86
+ in a fashion requiring copyright permission, other than the making of an
87
+ exact copy. The resulting work is called a "modified version" of the
88
+ earlier work or a work "based on" the earlier work.
89
+
90
+ A "covered work" means either the unmodified Program or a work based
91
+ on the Program.
92
+
93
+ To "propagate" a work means to do anything with it that, without
94
+ permission, would make you directly or secondarily liable for
95
+ infringement under applicable copyright law, except executing it on a
96
+ computer or modifying a private copy. Propagation includes copying,
97
+ distribution (with or without modification), making available to the
98
+ public, and in some countries other activities as well.
99
+
100
+ To "convey" a work means any kind of propagation that enables other
101
+ parties to make or receive copies. Mere interaction with a user through
102
+ a computer network, with no transfer of a copy, is not conveying.
103
+
104
+ An interactive user interface displays "Appropriate Legal Notices"
105
+ to the extent that it includes a convenient and prominently visible
106
+ feature that (1) displays an appropriate copyright notice, and (2)
107
+ tells the user that there is no warranty for the work (except to the
108
+ extent that warranties are provided), that licensees may convey the
109
+ work under this License, and how to view a copy of this License. If
110
+ the interface presents a list of user commands or options, such as a
111
+ menu, a prominent item in the list meets this criterion.
112
+
113
+ 1. Source Code.
114
+
115
+ The "source code" for a work means the preferred form of the work
116
+ for making modifications to it. "Object code" means any non-source
117
+ form of a work.
118
+
119
+ A "Standard Interface" means an interface that either is an official
120
+ standard defined by a recognized standards body, or, in the case of
121
+ interfaces specified for a particular programming language, one that
122
+ is widely used among developers working in that language.
123
+
124
+ The "System Libraries" of an executable work include anything, other
125
+ than the work as a whole, that (a) is included in the normal form of
126
+ packaging a Major Component, but which is not part of that Major
127
+ Component, and (b) serves only to enable use of the work with that
128
+ Major Component, or to implement a Standard Interface for which an
129
+ implementation is available to the public in source code form. A
130
+ "Major Component", in this context, means a major essential component
131
+ (kernel, window system, and so on) of the specific operating system
132
+ (if any) on which the executable work runs, or a compiler used to
133
+ produce the work, or an object code interpreter used to run it.
134
+
135
+ The "Corresponding Source" for a work in object code form means all
136
+ the source code needed to generate, install, and (for an executable
137
+ work) run the object code and to modify the work, including scripts to
138
+ control those activities. However, it does not include the work's
139
+ System Libraries, or general-purpose tools or generally available free
140
+ programs which are used unmodified in performing those activities but
141
+ which are not part of the work. For example, Corresponding Source
142
+ includes interface definition files associated with source files for
143
+ the work, and the source code for shared libraries and dynamically
144
+ linked subprograms that the work is specifically designed to require,
145
+ such as by intimate data communication or control flow between those
146
+ subprograms and other parts of the work.
147
+
148
+ The Corresponding Source need not include anything that users
149
+ can regenerate automatically from other parts of the Corresponding
150
+ Source.
151
+
152
+ The Corresponding Source for a work in source code form is that
153
+ same work.
154
+
155
+ 2. Basic Permissions.
156
+
157
+ All rights granted under this License are granted for the term of
158
+ copyright on the Program, and are irrevocable provided the stated
159
+ conditions are met. This License explicitly affirms your unlimited
160
+ permission to run the unmodified Program. The output from running a
161
+ covered work is covered by this License only if the output, given its
162
+ content, constitutes a covered work. This License acknowledges your
163
+ rights of fair use or other equivalent, as provided by copyright law.
164
+
165
+ You may make, run and propagate covered works that you do not
166
+ convey, without conditions so long as your license otherwise remains
167
+ in force. You may convey covered works to others for the sole purpose
168
+ of having them make modifications exclusively for you, or provide you
169
+ with facilities for running those works, provided that you comply with
170
+ the terms of this License in conveying all material for which you do
171
+ not control copyright. Those thus making or running the covered works
172
+ for you must do so exclusively on your behalf, under your direction
173
+ and control, on terms that prohibit them from making any copies of
174
+ your copyrighted material outside their relationship with you.
175
+
176
+ Conveying under any other circumstances is permitted solely under
177
+ the conditions stated below. Sublicensing is not allowed; section 10
178
+ makes it unnecessary.
179
+
180
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
181
+
182
+ No covered work shall be deemed part of an effective technological
183
+ measure under any applicable law fulfilling obligations under article
184
+ 11 of the WIPO copyright treaty adopted on 20 December 1996, or
185
+ similar laws prohibiting or restricting circumvention of such
186
+ measures.
187
+
188
+ When you convey a covered work, you waive any legal power to forbid
189
+ circumvention of technological measures to the extent such circumvention
190
+ is effected by exercising rights under this License with respect to
191
+ the covered work, and you disclaim any intention to limit operation or
192
+ modification of the work as a means of enforcing, against the work's
193
+ users, your or third parties' legal rights to forbid circumvention of
194
+ technological measures.
195
+
196
+ 4. Conveying Verbatim Copies.
197
+
198
+ You may convey verbatim copies of the Program's source code as you
199
+ receive it, in any medium, provided that you conspicuously and
200
+ appropriately publish on each copy an appropriate copyright notice;
201
+ keep intact all notices stating that this License and any
202
+ non-permissive terms added in accord with section 7 apply to the code;
203
+ keep intact all notices of the absence of any warranty; and give all
204
+ recipients a copy of this License along with the Program.
205
+
206
+ You may charge any price or no price for each copy that you convey,
207
+ and you may offer support or warranty protection for a fee.
208
+
209
+ 5. Conveying Modified Source Versions.
210
+
211
+ You may convey a work based on the Program, or the modifications to
212
+ produce it from the Program, in the form of source code under the
213
+ terms of section 4, provided that you also meet all of these conditions:
214
+
215
+ a) The work must carry prominent notices stating that you modified
216
+ it, and giving a relevant date.
217
+
218
+ b) The work must carry prominent notices stating that it is
219
+ released under this License and any conditions added under section
220
+ 7. This requirement modifies the requirement in section 4 to
221
+ "keep intact all notices".
222
+
223
+ c) You must license the entire work, as a whole, under this
224
+ License to anyone who comes into possession of a copy. This
225
+ License will therefore apply, along with any applicable section 7
226
+ additional terms, to the whole of the work, and all its parts,
227
+ regardless of how they are packaged. This License gives no
228
+ permission to license the work in any other way, but it does not
229
+ invalidate such permission if you have separately received it.
230
+
231
+ d) If the work has interactive user interfaces, each must display
232
+ Appropriate Legal Notices; however, if the Program has interactive
233
+ interfaces that do not display Appropriate Legal Notices, your
234
+ work need not make them do so.
235
+
236
+ A compilation of a covered work with other separate and independent
237
+ works, which are not by their nature extensions of the covered work,
238
+ and which are not combined with it such as to form a larger program,
239
+ in or on a volume of a storage or distribution medium, is called an
240
+ "aggregate" if the compilation and its resulting copyright are not
241
+ used to limit the access or legal rights of the compilation's users
242
+ beyond what the individual works permit. Inclusion of a covered work
243
+ in an aggregate does not cause this License to apply to the other
244
+ parts of the aggregate.
245
+
246
+ 6. Conveying Non-Source Forms.
247
+
248
+ You may convey a covered work in object code form under the terms
249
+ of sections 4 and 5, provided that you also convey the
250
+ machine-readable Corresponding Source under the terms of this License,
251
+ in one of these ways:
252
+
253
+ a) Convey the object code in, or embodied in, a physical product
254
+ (including a physical distribution medium), accompanied by the
255
+ Corresponding Source fixed on a durable physical medium
256
+ customarily used for software interchange.
257
+
258
+ b) Convey the object code in, or embodied in, a physical product
259
+ (including a physical distribution medium), accompanied by a
260
+ written offer, valid for at least three years and valid for as
261
+ long as you offer spare parts or customer support for that product
262
+ model, to give anyone who possesses the object code either (1) a
263
+ copy of the Corresponding Source for all the software in the
264
+ product that is covered by this License, on a durable physical
265
+ medium customarily used for software interchange, for a price no
266
+ more than your reasonable cost of physically performing this
267
+ conveying of source, or (2) access to copy the
268
+ Corresponding Source from a network server at no charge.
269
+
270
+ c) Convey individual copies of the object code with a copy of the
271
+ written offer to provide the Corresponding Source. This
272
+ alternative is allowed only occasionally and noncommercially, and
273
+ only if you received the object code with such an offer, in accord
274
+ with subsection 6b.
275
+
276
+ d) Convey the object code by offering access from a designated
277
+ place (gratis or for a charge), and offer equivalent access to the
278
+ Corresponding Source in the same way through the same place at no
279
+ further charge. You need not require recipients to copy the
280
+ Corresponding Source along with the object code. If the place to
281
+ copy the object code is a network server, the Corresponding Source
282
+ may be on a different server (operated by you or a third party)
283
+ that supports equivalent copying facilities, provided you maintain
284
+ clear directions next to the object code saying where to find the
285
+ Corresponding Source. Regardless of what server hosts the
286
+ Corresponding Source, you remain obligated to ensure that it is
287
+ available for as long as needed to satisfy these requirements.
288
+
289
+ e) Convey the object code using peer-to-peer transmission, provided
290
+ you inform other peers where the object code and Corresponding
291
+ Source of the work are being offered to the general public at no
292
+ charge under subsection 6d.
293
+
294
+ A separable portion of the object code, whose source code is excluded
295
+ from the Corresponding Source as a System Library, need not be
296
+ included in conveying the object code work.
297
+
298
+ A "User Product" is either (1) a "consumer product", which means any
299
+ tangible personal property which is normally used for personal, family,
300
+ or household purposes, or (2) anything designed or sold for incorporation
301
+ into a dwelling. In determining whether a product is a consumer product,
302
+ doubtful cases shall be resolved in favor of coverage. For a particular
303
+ product received by a particular user, "normally used" refers to a
304
+ typical or common use of that class of product, regardless of the status
305
+ of the particular user or of the way in which the particular user
306
+ actually uses, or expects or is expected to use, the product. A product
307
+ is a consumer product regardless of whether the product has substantial
308
+ commercial, industrial or non-consumer uses, unless such uses represent
309
+ the only significant mode of use of the product.
310
+
311
+ "Installation Information" for a User Product means any methods,
312
+ procedures, authorization keys, or other information required to install
313
+ and execute modified versions of a covered work in that User Product from
314
+ a modified version of its Corresponding Source. The information must
315
+ suffice to ensure that the continued functioning of the modified object
316
+ code is in no case prevented or interfered with solely because
317
+ modification has been made.
318
+
319
+ If you convey an object code work under this section in, or with, or
320
+ specifically for use in, a User Product, and the conveying occurs as
321
+ part of a transaction in which the right of possession and use of the
322
+ User Product is transferred to the recipient in perpetuity or for a
323
+ fixed term (regardless of how the transaction is characterized), the
324
+ Corresponding Source conveyed under this section must be accompanied
325
+ by the Installation Information. But this requirement does not apply
326
+ if neither you nor any third party retains the ability to install
327
+ modified object code on the User Product (for example, the work has
328
+ been installed in ROM).
329
+
330
+ The requirement to provide Installation Information does not include a
331
+ requirement to continue to provide support service, warranty, or updates
332
+ for a work that has been modified or installed by the recipient, or for
333
+ the User Product in which it has been modified or installed. Access to a
334
+ network may be denied when the modification itself materially and
335
+ adversely affects the operation of the network or violates the rules and
336
+ protocols for communication across the network.
337
+
338
+ Corresponding Source conveyed, and Installation Information provided,
339
+ in accord with this section must be in a format that is publicly
340
+ documented (and with an implementation available to the public in
341
+ source code form), and must require no special password or key for
342
+ unpacking, reading or copying.
343
+
344
+ 7. Additional Terms.
345
+
346
+ "Additional permissions" are terms that supplement the terms of this
347
+ License by making exceptions from one or more of its conditions.
348
+ Additional permissions that are applicable to the entire Program shall
349
+ be treated as though they were included in this License, to the extent
350
+ that they are valid under applicable law. If additional permissions
351
+ apply only to part of the Program, that part may be used separately
352
+ under those permissions, but the entire Program remains governed by
353
+ this License without regard to the additional permissions.
354
+
355
+ When you convey a copy of a covered work, you may at your option
356
+ remove any additional permissions from that copy, or from any part of
357
+ it. (Additional permissions may be written to require their own
358
+ removal in certain cases when you modify the work.) You may place
359
+ additional permissions on material, added by you to a covered work,
360
+ for which you have or can give appropriate copyright permission.
361
+
362
+ Notwithstanding any other provision of this License, for material you
363
+ add to a covered work, you may (if authorized by the copyright holders of
364
+ that material) supplement the terms of this License with terms:
365
+
366
+ a) Disclaiming warranty or limiting liability differently from the
367
+ terms of sections 15 and 16 of this License; or
368
+
369
+ b) Requiring preservation of specified reasonable legal notices or
370
+ author attributions in that material or in the Appropriate Legal
371
+ Notices displayed by works containing it; or
372
+
373
+ c) Prohibiting misrepresentation of the origin of that material, or
374
+ requiring that modified versions of such material be marked in
375
+ reasonable ways as different from the original version; or
376
+
377
+ d) Limiting the use for publicity purposes of names of licensors or
378
+ authors of the material; or
379
+
380
+ e) Declining to grant rights under trademark law for use of some
381
+ trade names, trademarks, or service marks; or
382
+
383
+ f) Requiring indemnification of licensors and authors of that
384
+ material by anyone who conveys the material (or modified versions of
385
+ it) with contractual assumptions of liability to the recipient, for
386
+ any liability that these contractual assumptions directly impose on
387
+ those licensors and authors.
388
+
389
+ All other non-permissive additional terms are considered "further
390
+ restrictions" within the meaning of section 10. If the Program as you
391
+ received it, or any part of it, contains a notice stating that it is
392
+ governed by this License along with a term that is a further
393
+ restriction, you may remove that term. If a license document contains
394
+ a further restriction but permits relicensing or conveying under this
395
+ License, you may add to a covered work material governed by the terms
396
+ of that license document, provided that the further restriction does
397
+ not survive such relicensing or conveying.
398
+
399
+ If you add terms to a covered work in accord with this section, you
400
+ must place, in the relevant source files, a statement of the
401
+ additional terms that apply to those files, or a notice indicating
402
+ where to find the applicable terms.
403
+
404
+ Additional terms, permissive or non-permissive, may be stated in the
405
+ form of a separately written license, or stated as exceptions;
406
+ the above requirements apply either way.
407
+
408
+ 8. Termination.
409
+
410
+ You may not propagate or modify a covered work except as expressly
411
+ provided under this License. Any attempt otherwise to propagate or
412
+ modify it is void, and will automatically terminate your rights under
413
+ this License (including any patent licenses granted under the third
414
+ paragraph of section 11).
415
+
416
+ However, if you cease all violation of this License, then your
417
+ license from a particular copyright holder is reinstated (a)
418
+ provisionally, unless and until the copyright holder explicitly and
419
+ finally terminates your license, and (b) permanently, if the copyright
420
+ holder fails to notify you of the violation by some reasonable means
421
+ prior to 60 days after the cessation.
422
+
423
+ Moreover, your license from a particular copyright holder is
424
+ reinstated permanently if the copyright holder notifies you of the
425
+ violation by some reasonable means, this is the first time you have
426
+ received notice of violation of this License (for any work) from that
427
+ copyright holder, and you cure the violation prior to 30 days after
428
+ your receipt of the notice.
429
+
430
+ Termination of your rights under this section does not terminate the
431
+ licenses of parties who have received copies or rights from you under
432
+ this License. If your rights have been terminated and not permanently
433
+ reinstated, you do not qualify to receive new licenses for the same
434
+ material under section 10.
435
+
436
+ 9. Acceptance Not Required for Having Copies.
437
+
438
+ You are not required to accept this License in order to receive or
439
+ run a copy of the Program. Ancillary propagation of a covered work
440
+ occurring solely as a consequence of using peer-to-peer transmission
441
+ to receive a copy likewise does not require acceptance. However,
442
+ nothing other than this License grants you permission to propagate or
443
+ modify any covered work. These actions infringe copyright if you do
444
+ not accept this License. Therefore, by modifying or propagating a
445
+ covered work, you indicate your acceptance of this License to do so.
446
+
447
+ 10. Automatic Licensing of Downstream Recipients.
448
+
449
+ Each time you convey a covered work, the recipient automatically
450
+ receives a license from the original licensors, to run, modify and
451
+ propagate that work, subject to this License. You are not responsible
452
+ for enforcing compliance by third parties with this License.
453
+
454
+ An "entity transaction" is a transaction transferring control of an
455
+ organization, or substantially all assets of one, or subdividing an
456
+ organization, or merging organizations. If propagation of a covered
457
+ work results from an entity transaction, each party to that
458
+ transaction who receives a copy of the work also receives whatever
459
+ licenses to the work the party's predecessor in interest had or could
460
+ give under the previous paragraph, plus a right to possession of the
461
+ Corresponding Source of the work from the predecessor in interest, if
462
+ the predecessor has it or can get it with reasonable efforts.
463
+
464
+ You may not impose any further restrictions on the exercise of the
465
+ rights granted or affirmed under this License. For example, you may
466
+ not impose a license fee, royalty, or other charge for exercise of
467
+ rights granted under this License, and you may not initiate litigation
468
+ (including a cross-claim or counterclaim in a lawsuit) alleging that
469
+ any patent claim is infringed by making, using, selling, offering for
470
+ sale, or importing the Program or any portion of it.
471
+
472
+ 11. Patents.
473
+
474
+ A "contributor" is a copyright holder who authorizes use under this
475
+ License of the Program or a work on which the Program is based. The
476
+ work thus licensed is called the contributor's "contributor version".
477
+
478
+ A contributor's "essential patent claims" are all patent claims
479
+ owned or controlled by the contributor, whether already acquired or
480
+ hereafter acquired, that would be infringed by some manner, permitted
481
+ by this License, of making, using, or selling its contributor version,
482
+ but do not include claims that would be infringed only as a
483
+ consequence of further modification of the contributor version. For
484
+ purposes of this definition, "control" includes the right to grant
485
+ patent sublicenses in a manner consistent with the requirements of
486
+ this License.
487
+
488
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
489
+ patent license under the contributor's essential patent claims, to
490
+ make, use, sell, offer for sale, import and otherwise run, modify and
491
+ propagate the contents of its contributor version.
492
+
493
+ In the following three paragraphs, a "patent license" is any express
494
+ agreement or commitment, however denominated, not to enforce a patent
495
+ (such as an express permission to practice a patent or covenant not to
496
+ sue for patent infringement). To "grant" such a patent license to a
497
+ party means to make such an agreement or commitment not to enforce a
498
+ patent against the party.
499
+
500
+ If you convey a covered work, knowingly relying on a patent license,
501
+ and the Corresponding Source of the work is not available for anyone
502
+ to copy, free of charge and under the terms of this License, through a
503
+ publicly available network server or other readily accessible means,
504
+ then you must either (1) cause the Corresponding Source to be so
505
+ available, or (2) arrange to deprive yourself of the benefit of the
506
+ patent license for this particular work, or (3) arrange, in a manner
507
+ consistent with the requirements of this License, to extend the patent
508
+ license to downstream recipients. "Knowingly relying" means you have
509
+ actual knowledge that, but for the patent license, your conveying the
510
+ covered work in a country, or your recipient's use of the covered work
511
+ in a country, would infringe one or more identifiable patents in that
512
+ country that you have reason to believe are valid.
513
+
514
+ If, pursuant to or in connection with a single transaction or
515
+ arrangement, you convey, or propagate by procuring conveyance of, a
516
+ covered work, and grant a patent license to some of the parties
517
+ receiving the covered work authorizing them to use, propagate, modify
518
+ or convey a specific copy of the covered work, then the patent license
519
+ you grant is automatically extended to all recipients of the covered
520
+ work and works based on it.
521
+
522
+ A patent license is "discriminatory" if it does not include within
523
+ the scope of its coverage, prohibits the exercise of, or is
524
+ conditioned on the non-exercise of one or more of the rights that are
525
+ specifically granted under this License. You may not convey a covered
526
+ work if you are a party to an arrangement with a third party that is
527
+ in the business of distributing software, under which you make payment
528
+ to the third party based on the extent of your activity of conveying
529
+ the work, and under which the third party grants, to any of the
530
+ parties who would receive the covered work from you, a discriminatory
531
+ patent license (a) in connection with copies of the covered work
532
+ conveyed by you (or copies made from those copies), or (b) primarily
533
+ for and in connection with specific products or compilations that
534
+ contain the covered work, unless you entered into that arrangement,
535
+ or that patent license was granted, prior to 28 March 2007.
536
+
537
+ Nothing in this License shall be construed as excluding or limiting
538
+ any implied license or other defenses to infringement that may
539
+ otherwise be available to you under applicable patent law.
540
+
541
+ 12. No Surrender of Others' Freedom.
542
+
543
+ If conditions are imposed on you (whether by court order, agreement or
544
+ otherwise) that contradict the conditions of this License, they do not
545
+ excuse you from the conditions of this License. If you cannot convey a
546
+ covered work so as to satisfy simultaneously your obligations under this
547
+ License and any other pertinent obligations, then as a consequence you may
548
+ not convey it at all. For example, if you agree to terms that obligate you
549
+ to collect a royalty for further conveying from those to whom you convey
550
+ the Program, the only way you could satisfy both those terms and this
551
+ License would be to refrain entirely from conveying the Program.
552
+
553
+ 13. Use with the GNU Affero General Public License.
554
+
555
+ Notwithstanding any other provision of this License, you have
556
+ permission to link or combine any covered work with a work licensed
557
+ under version 3 of the GNU Affero General Public License into a single
558
+ combined work, and to convey the resulting work. The terms of this
559
+ License will continue to apply to the part which is the covered work,
560
+ but the special requirements of the GNU Affero General Public License,
561
+ section 13, concerning interaction through a network will apply to the
562
+ combination as such.
563
+
564
+ 14. Revised Versions of this License.
565
+
566
+ The Free Software Foundation may publish revised and/or new versions of
567
+ the GNU General Public License from time to time. Such new versions will
568
+ be similar in spirit to the present version, but may differ in detail to
569
+ address new problems or concerns.
570
+
571
+ Each version is given a distinguishing version number. If the
572
+ Program specifies that a certain numbered version of the GNU General
573
+ Public License "or any later version" applies to it, you have the
574
+ option of following the terms and conditions either of that numbered
575
+ version or of any later version published by the Free Software
576
+ Foundation. If the Program does not specify a version number of the
577
+ GNU General Public License, you may choose any version ever published
578
+ by the Free Software Foundation.
579
+
580
+ If the Program specifies that a proxy can decide which future
581
+ versions of the GNU General Public License can be used, that proxy's
582
+ public statement of acceptance of a version permanently authorizes you
583
+ to choose that version for the Program.
584
+
585
+ Later license versions may give you additional or different
586
+ permissions. However, no additional obligations are imposed on any
587
+ author or copyright holder as a result of your choosing to follow a
588
+ later version.
589
+
590
+ 15. Disclaimer of Warranty.
591
+
592
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
593
+ APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
594
+ HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
595
+ OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
596
+ THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
597
+ PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
598
+ IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
599
+ ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
600
+
601
+ 16. Limitation of Liability.
602
+
603
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
604
+ WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
605
+ THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
606
+ GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
607
+ USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
608
+ DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
609
+ PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
610
+ EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
611
+ SUCH DAMAGES.
612
+
613
+ 17. Interpretation of Sections 15 and 16.
614
+
615
+ If the disclaimer of warranty and limitation of liability provided
616
+ above cannot be given local legal effect according to their terms,
617
+ reviewing courts shall apply local law that most closely approximates
618
+ an absolute waiver of all civil liability in connection with the
619
+ Program, unless a warranty or assumption of liability accompanies a
620
+ copy of the Program in return for a fee.
621
+
622
+ END OF TERMS AND CONDITIONS
623
+
624
+ How to Apply These Terms to Your New Programs
625
+
626
+ If you develop a new program, and you want it to be of the greatest
627
+ possible use to the public, the best way to achieve this is to make it
628
+ free software which everyone can redistribute and change under these terms.
629
+
630
+ To do so, attach the following notices to the program. It is safest
631
+ to attach them to the start of each source file to most effectively
632
+ state the exclusion of warranty; and each file should have at least
633
+ the "copyright" line and a pointer to where the full notice is found.
634
+
635
+ <one line to give the program's name and a brief idea of what it does.>
636
+ Copyright (C) <year> <name of author>
637
+
638
+ This program is free software: you can redistribute it and/or modify
639
+ it under the terms of the GNU General Public License as published by
640
+ the Free Software Foundation, either version 3 of the License, or
641
+ (at your option) any later version.
642
+
643
+ This program is distributed in the hope that it will be useful,
644
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
645
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
646
+ GNU General Public License for more details.
647
+
648
+ You should have received a copy of the GNU General Public License
649
+ along with this program. If not, see <http://www.gnu.org/licenses/>.
650
+
651
+ Also add information on how to contact you by electronic and paper mail.
652
+
653
+ If the program does terminal interaction, make it output a short
654
+ notice like this when it starts in an interactive mode:
655
+
656
+ <program> Copyright (C) <year> <name of author>
657
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
658
+ This is free software, and you are welcome to redistribute it
659
+ under certain conditions; type `show c' for details.
660
+
661
+ The hypothetical commands `show w' and `show c' should show the appropriate
662
+ parts of the General Public License. Of course, your program's commands
663
+ might be different; for a GUI interface, you would use an "about box".
664
+
665
+ You should also get your employer (if you work as a programmer) or school,
666
+ if any, to sign a "copyright disclaimer" for the program, if necessary.
667
+ For more information on this, and how to apply and follow the GNU GPL, see
668
+ <http://www.gnu.org/licenses/>.
669
+
670
+ The GNU General Public License does not permit incorporating your program
671
+ into proprietary programs. If your program is a subroutine library, you
672
+ may consider it more useful to permit linking proprietary applications with
673
+ the library. If this is what you want to do, use the GNU Lesser General
674
+ Public License instead of this License. But first, please read
675
+ <http://www.gnu.org/philosophy/why-not-lgpl.html>.