1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
lib = File.expand_path("lib", __dir__)
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
require "chef-utils/version"
Gem::Specification.new do |spec|
spec.name = "chef-utils"
spec.version = ChefUtils::VERSION
spec.authors = ["Chef Software, Inc"]
spec.email = ["oss@chef.io"]
spec.summary = %q{Basic utility functions for Core Chef development}
spec.homepage = "https://github.com/chef/chef/tree/master/chef-utils"
spec.license = "Apache-2.0"
spec.metadata = {
"bug_tracker_uri" => "https://github.com/chef/chef/issues",
"changelog_uri" => "https://github.com/chef/chef/CHANGELOG.md",
"documentation_uri" => "https://github.com/chef/chef/tree/master/chef-utils/README.md",
"homepage_uri" => "https://github.com/chef/chef/tree/master/chef-utils",
"source_code_uri" => "https://github.com/chef/chef/tree/master/chef-utils",
}
spec.require_paths = ["lib"]
#
# NOTE: DO NOT ADD RUNTIME DEPS TO OTHER CHEF ECOSYSTEM GEMS
# (e.g. chef, ohai, mixlib-anything, ffi-yajl, and IN PARTICULAR NOT chef-config)
#
# This is so that this set of common code can be reused in any other library without
# creating circular dependencies. If you find yourself wanting to do that you probably
# have a helper that should go into the library you want to declare a dependency on,
# or you need to create another gem that is not this one. You may also want to rub some
# dependency injection on your API to invert things so that you don't have to take
# a dependency on the thing you need (i.e. allow injecting a hash-like thing instead of taking
# a dep on mixlib-config and then require the consumer to wire up chef-config to your
# API). Same for mixlib-log and Chef::Log in general.
#
# ABSOLUTELY NO EXCEPTIONS
#
spec.files = %w{Rakefile LICENSE} + Dir.glob("*.gemspec") +
Dir.glob("{lib,spec}/**/*", File::FNM_DOTMATCH).reject { |f| File.directory?(f) }
spec.bindir = "bin"
spec.executables = []
end
|
