guard-strainer 1.0.0

data/spec/fixtures/cookbooks/git/Berksfile

@@ -0,0 +1,8 @@
+site :opscode
+
+metadata
+
+group :integration do
+  cookbook "apt"
+  cookbook "yum"
+end

data/spec/fixtures/cookbooks/git/CHANGELOG.md

@@ -0,0 +1,76 @@
+## v2.5.2:
+
+### Bug
+
+- [COOK-2813]: Fix bad string interpolation in source recipe
+
+## v2.5.0:
+
+* Relax runit version constraint (now depend on 1.0+).
+
+## v2.4.0:
+
+* [COOK-2734] - update git versions
+## v2.3.0:
+
+* [COOK-2385] - update git::server for `runit_service` resource support
+
+## v2.2.0:
+
+* [COOK-2303] - git::server support for RHEL `platform_family`
+
+## v2.1.4:
+
+* [COOK-2110] - initial test-kitchen support (only available in GitHub
+  repository).
+* [COOK-2253] - pin runit dependency
+
+## v2.1.2:
+
+* [COOK-2043] - install git on ubuntu 12.04 not git-core
+
+## v2.1.0:
+
+The repository didn't have pushed commits, and so the following
+changes from earlier-than-latest versions wouldn't be available on the
+community site. We're releasing 2.1.0 to correct this.
+
+* [COOK-1943] - Update to git 1.8.0
+* [COOK-2020] - Add setup option attributes to Git Windows package
+  install
+
+## v2.0.0:
+
+This version uses `platform_family` attribute, making the cookbook incompatible
+with older versions of Chef/Ohai, hence the major version bump.
+
+* [COOK-1668] - git cookbook fails to run due to bad `platform_family`
+  call
+* [COOK-1759] - git::source needs additional package for rhel
+  `platform_family`
+
+## v1.1.2:
+
+* [COOK-2020] - Add setup option attributes to Git Windows package
+  install
+
+## v1.1.0:
+
+* [COOK-1943] - Update to git 1.8.0
+
+## v1.0.2:
+
+* [COOK-1537] - add recipe for source installation
+
+## v1.0.0:
+
+* [COOK-1152] - Add support for Mac OS X
+* [COOK-1112] - Add support for Windows
+
+## v0.10.0:
+
+* [COOK-853] - Git client installation on CentOS
+
+## v0.9.0:
+
+* Current public release.

data/spec/fixtures/cookbooks/git/CONTRIBUTING

@@ -0,0 +1,29 @@
+If you would like to contribute, please open a ticket in JIRA:
+
+* http://tickets.opscode.com
+
+Create the ticket in the COOK project and use the cookbook name as the
+component.
+
+For all code contributions, we ask that contributors sign a
+contributor license agreement (CLA). Instructions may be found here:
+
+* http://wiki.opscode.com/display/chef/How+to+Contribute
+
+When contributing changes to individual cookbooks, please do not
+modify the version number in the metadata.rb. Also please do not
+update the CHANGELOG.md for a new version. Not all changes to a
+cookbook may be merged and released in the same versions. Opscode will
+handle the version updates during the release process. You are welcome
+to correct typos or otherwise make updates to documentation in the
+README.
+
+If a contribution adds new platforms or platform versions, indicate
+such in the body of the commit message(s), and update the relevant
+COOK ticket. When writing commit messages, it is helpful for others if
+you indicate the COOK ticket. For example:
+
+    git commit -m '[COOK-1041] Updated pool resource to correctly delete.'
+
+In the ticket itself, it is also helpful if you include log output of
+a successful Chef run, but this is not absolutely required.

data/spec/fixtures/cookbooks/git/Gemfile

@@ -0,0 +1,3 @@
+source :rubygems
+
+gem 'test-kitchen', '< 1.0'

data/spec/fixtures/cookbooks/git/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/spec/fixtures/cookbooks/git/README.md

@@ -0,0 +1,115 @@
+Description
+===========
+
+Installs git and optionally sets up a git server as a daemon under runit.
+
+Requirements
+============
+## Ohai and Chef:
+
+* Ohai: 6.14.0+
+
+This cookbook makes use of `node['platform_family']` to simplify platform
+selection logic. This attribute was introduced in Ohai v0.6.12.
+
+## Platform:
+
+The following platform families are supported:
+
+* Debian
+* Arch
+* RHEL
+* Fedora
+* Mac OS X (10.6.0+)
+* Windows
+
+## Cookbooks:
+
+* runit (for `git::server`)
+* build-essential (for `git::source`)
+* dmg (for OS X installation)
+* yum (for RHEL 5 installation)
+
+### Windows Dependencies
+The [`windows_package`](https://github.com/opscode-cookbooks/windows#windows_package) resource from the Windows cookbook is required to
+install the git package on Windows.
+
+## Attributes
+
+### default
+The following attributes are platform-specific.
+
+#### Windows
+
+* `node['git']['version']` - git version to install
+* `node['git']['url']` - URL to git package
+* `node['git']['checksum']` - package SHA256 checksum
+* `node['git']['display_name']` - `windows_package` resource Display Name (makes the package install idempotent) 
+
+#### Mac OS X
+
+* `node['git']['osx_dmg']['url']` - URL to git package
+* `node['git']['osx_dmg']['checksum']` - package SHA256 checksum
+
+#### Linux
+
+* `node['git']['prefix']` - git install directory
+* `node['git']['version']` - git version to install
+* `node['git']['url']` - URL to git tarball
+* `node['git']['checksum']` - tarball SHA256 checksum
+
+Recipes
+=======
+
+## default
+
+Installs base git packages based on platform.
+
+## server
+
+Sets up a git daemon to provide a server.
+
+## source
+
+Installs git from source.
+
+## windows
+
+Installs git client on Windows
+
+Usage
+=====
+
+
+This cookbook primarily installs git core packages. It can also be
+used to serve git repositories.
+
+To install git client (all supported platforms):
+
+    include_recipe 'git'
+
+To install git server:
+
+    include_recipe "git::server"
+
+This creates the directory specified by git/server/base_path (default is /srv/git)
+and starts a git daemon, exporting all repositories found. Repositories need to be
+added manually, but will be available once they are created.
+
+License and Author
+==================
+
+- Author:: Joshua Timberman (<joshua@opscode.com>)
+- Copyright:: 2009-2012, Opscode, Inc.
+
+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/spec/fixtures/cookbooks/git/TESTING.md

@@ -0,0 +1,25 @@
+This cookbook includes support for running tests via Test Kitchen (1.0). This has some requirements.
+
+1. You must be using the Git repository, rather than the downloaded cookbook from the Chef Community Site.
+2. You must have Vagrant 1.1 installed.
+3. You must have a "sane" Ruby 1.9.3 environment.
+
+Once the above requirements are met, install the additional requirements:
+
+Install the berkshelf plugin for vagrant, and berkshelf to your local Ruby environment.
+
+    vagrant plugin install vagrant-berkshelf
+    gem install berkshelf
+
+Install Test Kitchen 1.0 (unreleased yet, use the alpha / prerelease version).
+
+    gem install test-kitchen --pre
+
+Install the Vagrant driver for Test Kitchen.
+
+    gem install kitchen-vagrant
+
+Once the above are installed, you should be able to run Test Kitchen:
+
+    kitchen list
+    kitchen test