From d4fd97756c28dfaa34f3229f1724f49a2e874851 Mon Sep 17 00:00:00 2001 From: Seth Chisamore Date: Tue, 15 Dec 2015 13:49:32 -0500 Subject: Use same package naming convention across Chef FIPS platforms We only name the Chef Windows package `chef-client*` (as opposed to `chef*` like all other platforms) for legacy reasons. There is no reason to create this same legacy issue out of the gate for the Chef FIPS package. --- config/projects/chef-fips.rb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config/projects/chef-fips.rb b/config/projects/chef-fips.rb index 7004630633..d61a217b6e 100644 --- a/config/projects/chef-fips.rb +++ b/config/projects/chef-fips.rb @@ -16,7 +16,7 @@ # # This is the chef client build with FIPS mode enabled. -# It's a stub for now and produces identical results +# It's a stub for now and produces identical results # chef_project_contents = IO.read(File.expand_path('../chef.rb', __FILE__)) self.instance_eval chef_project_contents @@ -29,7 +29,7 @@ if windows? # Native gems will use gcc which will barf on files with spaces, # which is only fixable if everyone in the world fixes their Makefiles install_dir "#{default_root}/opscode/#{name}" - package_name "chef-client-fips" + package_name "chef-fips" else install_dir "#{default_root}/#{name}" end -- cgit v1.2.1