buildpack-packager 2.3.4

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 4e85c65266998fe1e952c48e1734d1ca8b6e9709
+  data.tar.gz: ffba21b8055ec13b591f32ef3495e4fb0e10c5d6
+SHA512:
+  metadata.gz: 1078fca1adb589b73a37f7e349c8f4bbb56b5d4e913a28ef3b5e8c4c626c6783f8d207ea178195630caddc51c00f3d32c3bffb6b356b0299301f7684c2ae8b40
+  data.tar.gz: a2aa5e825f4d1c1cdddb8ad973ba19f5e20d153499678672ac498b86833b0f6921970a0519a7fbe5f835768b5b94d5a17694abeff75a8fce3d40c41be6b8358c

data/.gitignore

@@ -0,0 +1,14 @@
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/pkg/
+/spec/reports/
+/spec/**/*.zip
+/tmp/
+*.bundle
+*.so
+*.o
+*.a
+mkmf.log

data/.rspec

@@ -0,0 +1,2 @@
+--format documentation
+--color

data/Gemfile

@@ -0,0 +1,5 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in buildpack-packager.gemspec
+gemspec
+gem 'pry'

data/LICENSE

@@ -0,0 +1,176 @@
+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

data/README.md

@@ -0,0 +1,180 @@
+# Buildpack Packager
+
+A [RubyGem](https://rubygems.org/) that provides tooling to package a buildpack for upload to Cloud Foundry.
+
+For officially supported Cloud Foundry buildpacks, it is used in conjunction with [compile-extensions](https://github.com/cloudfoundry-incubator/compile-extensions).
+
+
+# Usage
+
+## Packaging a Buildpack
+
+Within your buildpack directory:
+
+1. Create a `Gemfile` and the line `gem 'buildpack-packager', git: 'https://github.com/cloudfoundry-incubator/buildpack-packager'`.
+1. Run `bundle install`.
+1. Create a `manifest.yml`
+1. Run the packager for uncached or cached mode:
+
+	```
+	buildpack-packager [cached|uncached]
+	```
+
+In either mode, the packager will add (almost) everything in your
+buildpack directory into a zip file.  It will exclude anything marked
+for exclusion in your manifest.
+
+In `cached` mode, the packager will download and add dependencies as
+described in the manifest.
+
+
+## Examining a manifest
+
+If you'd like to get a pretty-printed summary of what's in a manifest,
+run in `list` mode:
+
+```
+buildpack-packager list
+```
+
+Example output:
+
+```
++----------------------------+------------------------------+------------+
+| name                       | version                      | cf_stacks  |
++----------------------------+------------------------------+------------+
+| ruby                       | 2.0.0                        | cflinuxfs2 |
+| ruby                       | 2.1.5                        | cflinuxfs2 |
+| ruby                       | 2.1.6                        | cflinuxfs2 |
+| ruby                       | 2.2.1                        | cflinuxfs2 |
+| ruby                       | 2.2.2                        | cflinuxfs2 |
+| jruby                      | ruby-1.9.3-jruby-1.7.19      | cflinuxfs2 |
+| jruby                      | ruby-2.0.0-jruby-1.7.19      | cflinuxfs2 |
+| jruby                      | ruby-2.2.2-jruby-9.0.0.0.rc1 | cflinuxfs2 |
+| node                       | 0.12.2                       | cflinuxfs2 |
+| bundler                    | 1.9.7                        | cflinuxfs2 |
+| libyaml                    | 0.1.6                        | cflinuxfs2 |
+| openjdk1.8-latest          | -                            | cflinuxfs2 |
+| rails3_serve_static_assets | -                            | cflinuxfs2 |
+| rails_log_stdout           | -                            | cflinuxfs2 |
++----------------------------+------------------------------+------------+
+```
+
+### Option Flags
+
+#### --force-download
+
+By default, `buildpack-packager` stores the dependencies that it
+downloads while building a cached buildpack in a local cache at
+`~/.buildpack-packager`. This is in order to avoid redownloading them
+when repackaging similar buildpacks. Running `buildpack-packager
+cached` with the the `--force-download` option will force the packager
+to download dependencies from the s3 host and ignore the local cache.
+
+#### --use-custom-manifest
+
+If you would like to include a different manifest file in your
+packaged buildpack, you may call `buildpack-packager` with the the
+`--use-custom-manifest [path/to/manifest.yml]`
+option. `buildpack-packager` will generate a buildpack with the
+specified manifest. If you are building a cached buildpack,
+`buildpack-packager` will vendor dependencies from the specified
+manifest as well.
+
+
+# Manifest
+
+The packager looks for a `manifest.yml` file in the current working
+directory, which should be the root of your buildpack.
+
+A sample manifest (all keys are required):
+
+```yaml
+---
+language: ruby
+
+url_to_dependency_map:
+- match: bundler-(\d+\.\d+\.\d+)
+  name: bundler
+  version: $1
+- match: ruby-(\d+\.\d+\.\d+)
+  name: ruby
+  version: $1
+
+dependencies:
+  - name: bundler
+    version: 1.7.12
+    uri: https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/lucid64/bundler-1.7.12.tgz
+    md5: ab7ebd9c9e945e3ea91c8dd0c6aa3562
+    cf_stacks:
+      - lucid64
+      - cflinuxfs2
+  - name: ruby
+    version: 2.1.4
+    uri: https://pivotal-buildpacks.s3.amazonaws.com/ruby/binaries/lucid64/ruby-2.1.4.tgz
+    md5: 72b4d193a11766e2a4c45c1fed65754c
+    cf_stacks:
+      - lucid64
+      
+exclude_files:
+  - .gitignore
+  - private.key
+```
+
+## language (required)
+
+The language key is used to give your zip file a meaningful name.
+
+
+## url_to_dependency_map (required)
+
+A list of regular expressions that extract and map the values of `name` and `version` to a corresponding dependency. 
+
+
+## dependencies (required)
+
+
+The dependencies key specifies the name, version, uri, md5, and the
+cf_stacks (the root file system(s) for which it is compiled for) of a
+resource which the buildpack attempts to download during staging. By
+specifying them here, the packager can download them and install them
+into the `dependencies/` folder in the zip file.
+
+All keys are required:
+
+- `name`, `version`, and `uri`:
+Required for `url_to_dependency_map` to work. Make sure to create a new entry in the `url_to_dependency_map` if a matching regex does not exist for the dependency to be curled.
+
+- `md5`:
+Required to ensure that dependencies being packaged for 'cached' mode have not been compromised
+
+- `cf_stacks`:
+Required to ensure the right binary is selected for the root file system in which an app will be running on.  Currently supported root file systems are lucid64(default) and cflinuxfs2. *Note that if the same dependency is used for both root file systems, both can be listed under the `cf_stacks` key.*
+
+To have your buildpack use these 'cached' dependencies, use
+`compile_extensions/bin/translate_dependency_url` to translate the url
+into a locally cached url (useful for cached mode).
+
+Read more on the [compile-extensions repo](https://github.com/cloudfoundry-incubator/compile-extensions).
+
+
+## exclude_files (required)
+
+The exclude key lists files you do not want in your buildpack. This is
+useful to remove sensitive information or extraneous files before uploading.
+
+# Development
+
+## Propagating Packager Changes to CF Buildpacks
+
+Latest changes to master will not be automatically reflected in the various Cloud Foundry buildpacks.
+To propagate buildpack-packager changes:
+
+1. Update the version in `lib/buildpack/packager/version.rb`.
+2. Commit this change and push to master.
+3. Tag the new version with a release tag (e.g., `git tag v2.2.6`).
+4. Push the tag to origin with `git push --tags`.
+5. Update the `cf.Gemfile`s in the various buildpacks with the new release tag like so:
+```
+gem 'buildpack-packager', git: 'https://github.com/cloudfoundry/buildpack-packager', tag: 'v2.2.6'
+```

data/Rakefile

@@ -0,0 +1,6 @@
+require 'bundler/gem_tasks'
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new(:spec)
+
+task default: :spec

data/bin/buildpack-packager

@@ -0,0 +1,79 @@
+#!/usr/bin/env ruby
+require 'buildpack/packager'
+require 'optparse'
+require 'buildpack/manifest_validator'
+
+SUPPORTED_MODES = %w(cached uncached list defaults).freeze
+USAGE_MSG       = "USAGE: #{File.basename(__FILE__)} < #{SUPPORTED_MODES.map { |mode| '--' + mode }.join(' | ')} >".freeze
+
+options = {
+  root_dir:       Dir.pwd,
+  manifest_path:  'manifest.yml',
+  force_download: false
+}
+
+optparser = OptionParser.new do |opts|
+  opts.banner = USAGE_MSG
+
+  opts.on('--cached', 'Package dependencies with the built buildpack.') do
+    options[:mode] = :cached
+  end
+
+  opts.on('--uncached', 'Will NOT package dependencies with the built buildpack.') do
+    options[:mode] = :uncached
+  end
+
+  opts.on('--list', 'List dependencies supported by the buildpack.') do
+    options[:mode] = :list
+  end
+
+  opts.on('--defaults', 'List default dependency versions specified by the buildpack.') do
+    options[:mode] = :defaults
+  end
+
+  opts.on('--force-download', 'Force dependencies to be downloaded from the internet. (default is false)') do
+    options[:force_download] = true
+  end
+
+  opts.on('--use-custom-manifest=PATH_TO_MANIFEST', 'Use a custom manifest, passing the path as an argument.') do |manifest_path|
+    options[:manifest_path] = manifest_path
+  end
+
+  opts.on_tail('-h', '--help', 'Show this message') do
+    puts opts
+    exit
+  end
+end
+
+optparser.parse!
+
+unless options[:mode]
+  puts optparser
+  exit 1
+end
+
+manifest_path = options[:manifest_path]
+unless File.exist?(manifest_path)
+  STDERR.puts "Could not find #{manifest_path}"
+  exit 1
+end
+
+validator = Buildpack::ManifestValidator.new(manifest_path)
+unless validator.valid?
+  errors = validator.errors
+  if errors[:manifest_parser_errors]
+    STDERR.print "The manifest does not conform to the schema:\n\t- "
+    STDERR.puts errors[:manifest_parser_errors].join("\n\t- ")
+  end
+
+  STDERR.puts errors[:default_version].join("\n\t")
+  exit 1
+end
+
+if options[:mode] == :list
+  puts Buildpack::Packager.list(options)
+elsif options[:mode] == :defaults
+  puts Buildpack::Packager.defaults(options)
+else
+  Buildpack::Packager.package(options)
+end