husc 0.1.0

data/vendor/bundle/gems/mime-types-data-3.2019.1009/types/world.yaml

@@ -0,0 +1,8 @@
+---
+- !ruby/object:MIME::Type
+  content-type: x-world/x-vrml
+  encoding: base64
+  extensions:
+  - wrl
+  - vrml
+  registered: false

data/vendor/bundle/gems/mini_portile2-2.4.0/.concourse.yml

@@ -0,0 +1,83 @@
+---
+resources:
+- name: mini_portile
+  type: git
+  source:
+    uri: https://github.com/flavorjones/mini_portile
+    branch: master
+jobs:
+- name: "Minitest"
+  plan:
+  - get: mini_portile
+  - task: With version 1.9.3
+    config:
+      platform: linux
+      image: docker:///ruby#1.9.3
+      inputs:
+      - name: mini_portile
+      run:
+        path: bash
+        args:
+        - "-c"
+        - cd mini_portile && bundle install && rake
+    privileged: false
+  - task: With version 2.0
+    config:
+      platform: linux
+      image: docker:///ruby#2.0
+      inputs:
+      - name: mini_portile
+      run:
+        path: bash
+        args:
+        - "-c"
+        - cd mini_portile && bundle install && rake
+    privileged: false
+  - task: With version 2.1
+    config:
+      platform: linux
+      image: docker:///ruby#2.1
+      inputs:
+      - name: mini_portile
+      run:
+        path: bash
+        args:
+        - "-c"
+        - cd mini_portile && bundle install && rake
+    privileged: false
+  - task: With version 2.2
+    config:
+      platform: linux
+      image: docker:///ruby#2.2
+      inputs:
+      - name: mini_portile
+      run:
+        path: bash
+        args:
+        - "-c"
+        - cd mini_portile && bundle install && rake
+    privileged: false
+  - task: With version jruby-1.7.23
+    config:
+      platform: linux
+      image: docker:///jruby#1.7.23
+      inputs:
+      - name: mini_portile
+      run:
+        path: bash
+        args:
+        - "-c"
+        - cd mini_portile && bundle install && rake
+    privileged: false
+  - task: With version jruby-9.0.4.0
+    config:
+      platform: linux
+      image: docker:///jruby#9.0.4.0
+      inputs:
+      - name: mini_portile
+      run:
+        path: bash
+        args:
+        - "-c"
+        - cd mini_portile && bundle install && rake
+    privileged: false

data/vendor/bundle/gems/mini_portile2-2.4.0/.gitignore

@@ -0,0 +1,7 @@
+pkg
+tmp
+Gemfile.lock
+.bundle
+ports
+concourse/private.yml
+concourse/mini_portile.final.yml

data/vendor/bundle/gems/mini_portile2-2.4.0/.travis.yml

@@ -0,0 +1,15 @@
+---
+language: ruby
+sudo: false
+matrix:
+  include:
+  - rvm: 1.9.3
+  - rvm: 2.0
+  - rvm: 2.1
+  - rvm: 2.2.5
+  - rvm: 2.3.1
+  - rvm: 2.4.0
+    env:
+      - RUBYOPT="--enable-frozen-string-literal --debug=frozen-string-literal"
+  - rvm: jruby-1.7
+  - rvm: jruby-9.1.5.0

data/vendor/bundle/gems/mini_portile2-2.4.0/CHANGELOG.md

@@ -0,0 +1,209 @@
+### 2.4.0 / 2018-12-02
+
+#### Enhancements
+
+* Skip progress report when Content-Length is unavailable. [#85] (Thanks, @eagletmt!)
+
+
+### 2.3.0 / 2017-09-13
+
+#### Enhancements
+
+* Verify checksums of files at extraction time (in addition to at download time). (#56)
+* Clarify error message if a `tar` command can't be found. (#81)
+
+
+### 2.2.0 / 2017-06-04
+
+#### Enhancements
+
+* Remove MD5 hashing of configure options, not avialbale in FIPS mode. (#78)
+* Add experimental support for cmake-based projects.
+* Retry on HTTP failures during downloads. [#63] (Thanks, @jtarchie and @jvshahid!)
+* Support Ruby 2.4 frozen string literals.
+* Support applying patches for users with misconfigured git worktree. [#69]
+* Support gpg signature verification of download resources.
+
+
+### 2.1.0 / 2016-01-06
+
+#### Enhancements
+
+* Add support for `file:` protocol for tarballs
+
+
+#### Bugfixes
+
+* Raise exception on unsupported URI protocols
+* Ignore git whitespace config when patching (Thanks, @e2!) (#67)
+
+
+### 2.0.0 / 2015-11-30
+
+Many thanks to @larskanis, @knu, and @kirikak2, who all contributed
+code, ideas, or both to this release.
+
+Note that the 0.7.0.rc* series was not released as 0.7.0 final, and
+instead became 2.0.0 due to backwards-incompatible behavioral changes
+which can appear because rubygems doesn't enforce loading the declared
+dependency version at installation-time (only run-time).
+
+If you use MiniPortile in an `extconf.rb` file, please make sure you're
+setting a gem version constraint before `require "mini_portile2"` .
+
+Note also that 2.0.0 doesn't include the backwards-compatible "escaped
+string" behavior from 0.7.0.rc3.
+
+
+#### Enhancements
+
+* In patch task, use git(1) or patch(1), whichever is available.
+* Append outputs to patch.log instead of clobbering it for every patch command.
+* Take `configure_options` literally without running a subshell.
+  This changes allows for embedded spaces in a path, among other things.
+  Please unescape `configure_options` where you have been doing it yourself.
+* Print last 20 lines of the given log file, for convenience.
+* Allow SHA1, SHA256 and MD5 hash verification of downloads
+
+
+#### Bugfixes
+
+* Fix issue when proxy username/password use escaped characters.
+* Fix use of https and ftp proxy.
+
+
+### 0.7.0.rc4 / 2015-08-24
+
+* Updated tests for Windows. No functional change. Final release candidate?
+
+
+### 0.7.0.rc3 / 2015-08-24
+
+* Restore backwards-compatible behavior with respect to escaped strings.
+
+
+### 0.7.0.rc2 / 2015-08-24
+
+* Restore support for Ruby 1.9.2
+* Add Ruby 2.0.0 and Ruby 2.1.x to Appveyor suite
+
+
+### 0.7.0.rc1 / 2015-08-24
+
+Many thanks to @larskanis, @knu, and @kirikak2, who all contributed
+code, ideas, or both to this release.
+
+#### Enhancements
+
+* In patch task, use git(1) or patch(1), whichever is available.
+* Append outputs to patch.log instead of clobbering it for every patch command.
+* Take `configure_options` literally without running a subshell.
+  This changes allows for embedded spaces in a path, among other things.
+  Please unescape `configure_options` where you have been doing it yourself.
+* Print last 20 lines of the given log file, for convenience.
+* Allow SHA1, SHA256 and MD5 hash verification of downloads
+
+
+#### Bugfixes
+
+* Fix issue when proxy username/password use escaped characters.
+* Fix use of https and ftp proxy.
+
+
+### 0.6.2 / 2014-12-30
+
+* Updated gemspec, license and README to reflect new maintainer.
+
+
+### 0.6.1 / 2014-08-03
+
+* Enhancements:
+  * Expand path to logfile to easier debugging on failures.
+    Pull #33 [marvin2k]
+
+### 0.6.0 / 2014-04-18
+
+* Enhancements:
+  * Add default cert store and custom certs from `SSL_CERT_FILE` if present.
+    This increases compatibility with Ruby 1.8.7.
+
+* Bugfixes:
+  * Specify Accept-Encoding to make sure a raw file content is downloaded.
+    Pull #30. [knu]
+
+* Internal:
+  * Improve examples and use them as test harness.
+
+### 0.5.3 / 2014-03-24
+
+* Bugfixes:
+  * Shell escape paths in tar command. Pull #29. [quickshiftin]
+  * Support older versions of tar that cannot auto-detect
+    the compression type. Pull #27. Closes #21. [b-dean]
+  * Try RbConfig's CC before fall back to 'gcc'. Ref #28.
+
+### 0.5.2 / 2013-10-23
+
+* Bugfixes:
+  * Change tar detection order to support NetBSD 'gtar'. Closes #24
+  * Trick 'git-apply' when applying patches on nested Git checkouts. [larskanis]
+  * Respect ENV's MAKE before fallback to 'make'. [larskanis]
+  * Respect ENV's CC variable before fallback to 'gcc'.
+  * Avoid non-ASCII output of GCC cause host detection issues. Closes #22
+
+### 0.5.1 / 2013-07-07
+
+* Bugfixes:
+  * Detect tar executable without shelling out. [jtimberman]
+
+### 0.5.0 / 2012-11-17
+
+* Enhancements:
+  * Allow patching extracted files using `git apply`. [metaskills]
+
+### 0.4.1 / 2012-10-24
+
+* Bugfixes:
+  * Syntax to process FTp binary chunks differs between Ruby 1.8.7 and 1.9.x
+
+### 0.4.0 / 2012-10-24
+
+* Enhancements:
+  * Allow fetching of FTP URLs along HTTP ones. [metaskills]
+
+### 0.3.0 / 2012-03-23
+
+* Enhancements:
+  * Use `gcc -v` to determine original host (platform) instead of Ruby one.
+
+* Deprecations:
+  * Dropped support for Rubies older than 1.8.7
+
+### 0.2.2 / 2011-04-11
+
+* Minor enhancements:
+  * Use LDFLAGS when activating recipes for cross-compilation. Closes #6
+
+* Bugfixes:
+  * Remove memoization of *_path helpers. Closes #7
+
+### 0.2.1 / 2011-04-06
+
+* Minor enhancements:
+  * Provide MiniPortile#path to obtain full path to installation directory. Closes GH-5
+
+### 0.2.0 / 2011-04-05
+
+* Enhancements:
+  * Improve tar detection
+  * Improve and refactor configure_options
+  * Detect configure_options changes. Closes GH-1
+  * Add recipe examples
+
+* Bugfixes:
+  * MiniPortile#target can be changed now. Closes GH-2
+  * Always redirect tar output properly
+
+### 0.1.0 / 2011-03-08
+
+* Initial release. Welcome to this world!

data/vendor/bundle/gems/mini_portile2-2.4.0/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in mini_portile2.gemspec
+gemspec

data/vendor/bundle/gems/mini_portile2-2.4.0/LICENSE.txt

@@ -0,0 +1,20 @@
+Copyright (c) 2011-2016 Luis Lavena and Mike Dalessio
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/vendor/bundle/gems/mini_portile2-2.4.0/README.md

@@ -0,0 +1,245 @@
+# MiniPortile
+
+This documents versions 2 and up, for which the require file was
+renamed to `mini_portile2`. For mini_portile versions 0.6.x and
+previous, please visit
+[the v0.6.x branch](https://github.com/flavorjones/mini_portile/tree/v0.6.x).
+
+[![travis status](https://travis-ci.org/flavorjones/mini_portile.svg?branch=master)](https://travis-ci.org/flavorjones/mini_portile?branch=master)
+[![appveyor status](https://ci.appveyor.com/api/projects/status/509669xx1qlhqqab/branch/master?svg=true)](https://ci.appveyor.com/project/flavorjones/mini-portile/branch/master)
+
+* Documentation: http://www.rubydoc.info/github/flavorjones/mini_portile
+* Source Code: https://github.com/flavorjones/mini_portile
+* Bug Reports: https://github.com/flavorjones/mini_portile/issues
+
+This project is a minimalistic implementation of a port/recipe system
+**for developers**.
+
+Because _"Works on my machine"_ is unacceptable for a library maintainer.
+
+
+## Not Another Package Management System
+
+`mini_portile2` is not a general package management system. It is not
+aimed to replace apt, macports or homebrew.
+
+It's intended primarily to make sure that you, as the developer of a
+library, can reproduce a user's dependencies and environment by
+specifying a specific version of an underlying dependency that you'd
+like to use.
+
+So, if a user says, "This bug happens on my system that uses libiconv
+1.13.1", `mini_portile2` should make it easy for you to download,
+compile and link against libiconv 1.13.1; and run your test suite
+against it.
+
+This scenario might be simplified with something like this:
+
+```
+rake compile LIBICONV_VERSION=1.13.1
+```
+
+(For your homework, you can make libiconv version be taken from the
+appropriate `ENV` variables.)
+
+
+
+## Sounds easy, but where's the catch?
+
+At this time `mini_portile2` only supports **autoconf**- or
+**configure**-based projects. (That is, it assumes the library you
+want to build contains a `configure` script, which all the
+autoconf-based libraries do.)
+
+As of v2.2.0, there is experimental support for **CMake**-based
+projects. We welcome your feedback on this, particularly for Windows
+platforms.
+
+
+### How to use (for autoconf projects)
+
+Now that you know the catch, and you're still reading this, here is a
+quick example:
+
+```ruby
+gem "mini_portile2", "~> 2.0.0" # NECESSARY if used in extconf.rb. see below.
+require "mini_portile2"
+recipe = MiniPortile.new("libiconv", "1.13.1")
+recipe.files = ["http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.13.1.tar.gz"]
+recipe.cook
+recipe.activate
+```
+
+The gem version constraint makes sure that your extconf.rb is
+protected against possible backwards-incompatible changes to
+`mini_portile2`. This constraint is REQUIRED if you're using
+`mini_portile2` within a gem installation process (e.g., extconf.rb),
+because Bundler doesn't enforce gem version constraints at
+install-time (only at run-time.
+
+`#cook` will download, extract, patch, configure and compile the
+library into a namespaced structure.
+
+`#activate` ensures GCC will find this library and prefer it over a
+system-wide installation.
+
+
+### How to use (for cmake projects)
+
+Same as above, but instead of `MiniPortile.new`, call `MiniPortileCMake.new`.
+
+
+### Directory Structure Conventions
+
+`mini_portile2` follows the principle of **convention over configuration** and
+established a folder structure where is going to place files and perform work.
+
+Take the above example, and let's draw some picture:
+
+```
+mylib
+  |-- ports
+  |   |-- archives
+  |   |   `-- libiconv-1.13.1.tar.gz
+  |   `-- <platform>
+  |       `-- libiconv
+  |           `-- 1.13.1
+  |               |-- bin
+  |               |-- include
+  |               `-- lib
+  `-- tmp
+      `-- <platform>
+          `-- ports
+```
+
+In above structure, `<platform>` refers to the architecture that
+represents the operating system you're using (e.g. i686-linux,
+i386-mingw32, etc).
+
+Inside the platform folder, `mini_portile2` will store the artifacts
+that result from the compilation process. The library is versioned so
+you can keep multiple versions around on disk without clobbering
+anything.
+
+`archives` is where downloaded source files are cached. It is
+recommended you avoid trashing that folder to avoid downloading the
+same file multiple times (save bandwidth, save the world).
+
+`tmp` is where compilation is performed and can be safely discarded.
+
+Use the recipe's `#path` to obtain the full path to the installation
+directory:
+
+```ruby
+recipe.cook
+recipe.path # => /home/luis/projects/myapp/ports/i686-linux/libiconv/1.13.1
+```
+
+### How can I combine this with my compilation task?
+
+In the simplest case, your rake `compile` task will depend on
+`mini_portile2` compilation and most important, activation.
+
+Example:
+
+```ruby
+task :libiconv do
+  recipe = MiniPortile.new("libiconv", "1.13.1")
+  recipe.files << {
+    url: "http://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.13.1.tar.gz"],
+    sha256: "55a36168306089009d054ccdd9d013041bfc3ab26be7033d107821f1c4949a49"
+  }
+  checkpoint = ".#{recipe.name}-#{recipe.version}.installed"
+
+  unless File.exist?(checkpoint)
+    recipe.cook
+    touch checkpoint
+  end
+
+  recipe.activate
+end
+
+task :compile => [:libiconv] do
+  # ... your library's compilation task ...
+end
+```
+
+The above example will:
+
+* **download** and verify integrity the sources only once
+* **compile** the library only once (using a timestamp file)
+* ensure compiled library is **activated**
+* make the compile task depend upon compiled library activation
+
+As an exercise for the reader, you could specify the libiconv version
+in an environment variable or a configuration file.
+
+### Download verification
+MiniPortile supports HTTPS, HTTP, FTP and FILE sources for download.
+The integrity of the downloaded file can be verified per hash value or PGP signature.
+This is particular important for untrusted sources (non-HTTPS).
+
+#### Hash digest verification
+MiniPortile can verify the integrity of the downloaded file per SHA256, SHA1 or MD5 hash digest.
+
+```ruby
+  recipe.files << {
+    url: "http://your.host/file.tar.bz2",
+    sha256: "<32 byte hex value>",
+  }
+```
+
+#### PGP signature verification
+MiniPortile can also verify the integrity of the downloaded file per PGP signature.
+
+```ruby
+  public_key = <<-EOT
+    -----BEGIN PGP PUBLIC KEY BLOCK-----
+    Version: GnuPG v1
+
+    mQENBE7SKu8BCADQo6x4ZQfAcPlJMLmL8zBEBUS6GyKMMMDtrTh3Yaq481HB54oR
+    [...]
+    -----END PGP PUBLIC KEY BLOCK-----
+  EOT
+
+  recipe.files << {
+    url: "http://your.host/file.tar.bz2",
+    gpg: {
+      key: public_key,
+      signature_url: "http://your.host/file.tar.bz2.sig"
+    }
+  }
+```
+
+Please note, that the `gpg` executable is required to verify the signature.
+It is therefore recommended to use the hash verification method instead of PGP, when used in `extconf.rb` while `gem install`.
+
+### Native and/or Cross Compilation
+
+The above example covers the normal use case: compiling dependencies
+natively.
+
+`MiniPortile` also covers another use case, which is the
+cross-compilation of the dependencies to be used as part of a binary
+gem compilation.
+
+It is the perfect complementary tool for
+[`rake-compiler`](https://github.com/rake-compiler/rake-compiler) and
+its `cross` rake task.
+
+Depending on your usage of `rake-compiler`, you will need to use
+`host` to match the installed cross-compiler toolchain.
+
+Please refer to the examples directory for simplified and practical usage.
+
+
+### Supported Scenarios
+
+As mentioned before, `MiniPortile` requires a GCC compiler
+toolchain. This has been tested against Ubuntu, OSX and even Windows
+(RubyInstaller with DevKit)
+
+
+## License
+
+This library is licensed under MIT license. Please see LICENSE.txt for details.