omnibus-sonian 1.2.0.1

checksums.yaml

@@ -0,0 +1,15 @@
+---
+!binary "U0hBMQ==":
+  metadata.gz: !binary |-
+    ZmQ1OTJlOGY5NzZhZjFjMmNjNGY2OTFhODNkMmY2ZjNjNWNlODg3Mw==
+  data.tar.gz: !binary |-
+    NjZmY2NiZTBkMTdjZGU1NWJhMzZlOTg0M2IyMmNkNjE4NjJmZTM3Yw==
+!binary "U0hBNTEy":
+  metadata.gz: !binary |-
+    NDQ4ZWIyMzE5NmJmMmRjMmY4MmYwZjgwNDU1ZWFiNDBmYWI1M2FkMjI4ZmIw
+    OGMwZmNjZDZmMjA1MzQ2NDA0OTM1YTJjNmNiNzEwMDc2ZDNjYjBjNTg3NDYy
+    OTQxZGNkNDk4ZWM3MmEwZjEwMDMyN2RmMDA5N2RkMzI4MGNjOTM=
+  data.tar.gz: !binary |-
+    NjA4YzBmZmMyMTlkNjM4YWM2OWNmODUwMGQzNGIyYmEyMDI0OGIwZmU1MDc4
+    NTk2MjQ5MTNkODVlNDU5ZDZlZWM5MGY1MWJlMzA0ZjYyNzQyM2JlYWVlNjk3
+    YjY2ZWE1YzZiZjQ3YTU5OTMyODZkNTU1MmViNzU2MTlkODhiNjE=

data/.gitignore

@@ -0,0 +1,9 @@
+*.gem
+tmp
+
+# Bundler related
+Gemfile.lock
+.bundle/
+vendor/
+.yardoc
+doc/

data/.rspec

@@ -0,0 +1 @@
+--color --format doc

data/.travis.yml

@@ -0,0 +1,5 @@
+language: ruby
+rvm:
+  - 1.9.2
+  - 1.9.3
+script: rake spec

data/.yardopts

@@ -0,0 +1,6 @@
+--markup=markdown
+--markup-provider=redcarpet
+--readme=README.md
+-
+CHANGELOG.md
+LICENSE

data/CHANGELOG.md

@@ -0,0 +1,96 @@
+## 1.2.0 (July 12, 2013)
+
+FEATURES:
+
+* Add `whitelist_file` to software DSL. This allows an individual software 
+  definition to declare files that should be ignored during health checking.
+
+IMPROVEMENTS:
+
+* Raise an exception if a project's dependency is not found.
+
+BUG FIXES:
+
+* Properly load a project's transitive dependencies.
+* Ensure a component is only added to a library one time.
+
+## 1.1.1 (July 2, 2013)
+
+BUG FIXES:
+
+* Raise an exception if a patch file is not found.
+* Be more explicit about types in CPU computation.
+* Include pkg version, iteration, arch for solaris packages.
+* Fix assorted typos in CLI output.
+
+## 1.1.0 (June 12, 2013)
+
+FEATURES:
+
+* AIX health check whitelist support
+* AIX Backup-File Format (BFF) package support
+
+IMPROVEMENTS:
+
+* Add libstdc++ to SmartOS whitelist libs - this allows the health check pass when 
+  depending on C++ libs.
+
+BUG FIXES:
+
+* [CHEF-4246] - omnibus cache populate failing
+
+## 1.0.4 (May 23, 2013)
+
+FEATURES:
+
+* Add `release package` command which releases a single package with associated 
+  metadata file to a single S3 bucket.
+* Arch Linux health check whitelist support
+
+IMPROVEMENTS:
+
+* Add libstdc++ to Mac whitelist libs - this allows the health check pass when 
+  depending on C++ libs.
+* Change scope of `Omnibus::Library` instance from global to project.
+
+BUG FIXES:
+
+* [CHEF-4214] - projects in multi-project omnibus repositories share dependency scope
+
+## 1.0.3 (May 2, 2013)
+
+FEATURES:
+
+* [CHEF-2576] - SmartOS health check whitelist support
+* [CHEF-4141] - FreeBSD health check whitelist support
+* [CHEF-3990] - Add support to uncompress zip file
+
+BUG FIXES:
+
+* Fix project homepage in gemspec
+* Proper Thor 0.16.0, 0.17.0 suppport - Thor 0.18.0 renamed current_task to
+  current_command
+
+## 1.0.2 (April 23, 2013)
+
+IMPROVEMENTS:
+
+* Travis CI support
+
+BUG FIXES:
+
+* [CHEF-4112] `omnibus build project` command does not respect the
+  `--no-timestamp` flag
+
+## 1.0.1 (April 21, 2013)
+
+BUG FIXES:
+
+* Vagrant and Berkshelf Vagrant plugin version updates in generated project's
+  README.md. Current requirements for the virtualized build lab are:
+  * Vagrant 1.2.1+
+  * `vagrant-berkshelf` plugin (this was renamed from `berkshelf-vagrant`)
+
+## 1.0.0 (April 21, 2013)
+
+* The initial release.

data/Gemfile

@@ -0,0 +1,9 @@
+source "https://rubygems.org"
+
+gemspec
+
+group :docs do
+  gem "yard", "~> 0.8.5"
+  gem "redcarpet", "~> 2.2.2"
+  gem "github-markup", "~> 0.7.5"
+end

data/LICENSE

@@ -0,0 +1,201 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/NOTICE

@@ -0,0 +1,9 @@
+omnibus-ruby NOTICE
+===================
+
+Developed at Opscode (http://www.opscode.com).
+
+Contributors and Copyright holders:
+
+ * Copyright 2012, Opscode, Inc. <legal@opscode.com>
+

data/README.md

@@ -0,0 +1,195 @@
+## Omnibus
+
+[![Build Status](https://travis-ci.org/opscode/omnibus-ruby.png?branch=master)](https://travis-ci.org/opscode/omnibus-ruby)
+[![Code Climate](https://codeclimate.com/github/opscode/omnibus-ruby.png)](https://codeclimate.com/github/opscode/omnibus-ruby)
+
+Easily create full-stack installers for your project across a variety
+of platforms.
+
+Seth Chisamore and Christopher Maier of Opscode gave an introductory
+talk on Omnibus at ChefConf 2013, entitled **Eat the Whole Bowl:
+Building a Full-Stack Installer with Omnibus**
+([video](http://www.youtube.com/watch?v=q8iJAntXCNY),
+[slides](https://speakerdeck.com/schisamo/eat-the-whole-bowl-building-a-full-stack-installer-with-omnibus)).
+
+## Prerequisites
+
+Omnibus is designed to run with a minimal set of prerequisites. You'll
+need the following:
+
+- Ruby 1.9 or later (http://ruby-lang.org)
+- Bundler (http://gembundler.com, http://rubygems.org/gems/bundler)
+
+Though not *strictly* necessary, Vagrant makes using Omnibus easier,
+and is highly recommended.
+- Vagrant 1.2.1 or later (http://www.vagrantup.com)
+
+## Get Started
+
+Omnibus provides both a DSL for defining Omnibus projects for your
+software, as well as a command-line tool for generating installer
+artifacts from that definition.
+
+To get started, install Omnibus locally on your workstation.
+
+```
+$ gem install omnibus
+```
+
+You can now create an Omnibus project in your current directory by
+using the project generator feature.
+
+```
+$ omnibus project $MY_PROJECT_NAME
+```
+
+This will generate a complete project skeleton in the directory
+`omnibus-$MY_PROJECT_NAME`
+
+This minimal project will actually build.
+
+``` shell
+$ cd omnibus-$MY_PROJECT_NAME
+$ bundle install --binstubs
+$ bin/omnibus build project $MY_PROJECT_NAME
+```
+
+More details can be found in the generated project README file.
+
+## Configuration DSL
+
+Though the template project will build, it won't do anything exciting.
+For that, you'll need to use the Omnibus DSL to define the specifics
+of your own application.
+
+### Software
+
+Omnibus "software" files define individual software components that go
+into making your overall package.  They are the building blocks of
+your application.  The Software DSL provides a way to define where to
+retrieve the software sources, how to build them, and what
+dependencies they have.  These dependencies are also defined in their
+own Software DSL files, thus forming the basis for a dependency-aware
+build ordering.
+
+All Software definitions should go in the `config/software` directory
+of your Omnibus project repository.
+
+Opscode has created software definitions for a number of
+commonly-needed components, available in the
+[omnibus-software](https://github.com/opscode/omnibus-software.git)
+repository.  When you create a new project skeleton using Omnibus,
+this is automatically added to the project's Gemfile, making all these
+software definitions available to you.  (If you prefer, however, you
+can write your own versions of these same definitions in your project
+repository; local copies in `config/software` have precedence over
+anything from the `omnibus-software` repository.)
+
+An example:
+
+```ruby
+name    "ruby"
+version "1.9.2-p290"
+source  :url => "http://ftp.ruby-lang.org/pub/ruby/1.9/ruby-#{version}.tar.gz",
+        :md5 => "604da71839a6ae02b5b5b5e1b792d5eb"
+
+dependency "zlib"
+dependency "ncurses"
+dependency "openssl"
+
+relative_path "ruby-#{version}"
+
+build do
+  command "./configure"
+  command "make"
+  command "make install"
+end
+```
+
+Some of the DSL methods available include:
+
+**name**: The name of the software component.
+
+**version**: The version of the software component.
+
+**source**: Directions to the location of the source.
+
+**dependency**: An Omnibus software-defined component that this software depends on.
+
+**relative_path**: The relative path of the extracted tarball.
+
+**build**: The build instructions.
+
+**command**: An individual build step.
+
+For more, consult the documentation.
+
+### Projects
+
+A Project DSL file defines your actual application; this is the thing
+you are creating a full-stack installer for in the first place.  It
+provides a means to define the dependencies of the project (again, as
+specified in Software DSL definition files), as well as ways to set
+installer package metadata.
+
+All Project definitions (yes, you can have more than one) should go in
+the `config/projects` directory of your Omnibus project repository.
+
+```ruby
+name            "chef-full"
+maintainer      "YOUR NAME"
+homepage        "http://yoursite.com"
+
+install_path    "/opt/chef"
+build_version   "0.10.8"
+build_iteration 4
+
+dependency "chef"
+```
+
+Some DSL methods available include:
+
+**name:** The name of the project.
+
+**install_path:** The desired install location of the package.
+
+**build_version:** The package version.
+
+**build_iteration:** The package iteration number.
+
+**dependency**: An Omnibus software-defined component to include in this package.
+
+For more, see the documentation.
+
+## A Note On Builds
+
+As stated above, the generated project skeleton can run "as-is".
+However, Omnibus determines the platform for which to build an
+installer based on *the platform it is currently running on*.  That
+is, you can only generate a `.deb` file for Ubuntu if you're actually
+running Omnibus *on Ubuntu*.
+
+This is currently achieved using [Vagrant](http://www.vagrantup.com).
+A valid `Vagrantfile` for generating builds on Ubuntu and Centos
+platforms (though Omnibus is not limited to just those!) is created
+for each project that you generate using `omnibus project
+$MY_PROJECT_NAME`
+
+## License
+
+See the LICENSE and NOTICE files for more information.
+
+Copyright: Copyright (c) 2012--2013 Opscode, Inc.
+License: Apache License, Version 2.0
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.