From eb97aa5f7cbf3800a22849f29fad555b0ca042d9 Mon Sep 17 00:00:00 2001 From: Daniel Pittman Date: Mon, 31 Jan 2011 10:50:00 -0800 Subject: Bug #6091 -- test leading double-slash in filenames are allowed. They presently are not; this ensures that we verify that before merging a change that fixes bugs in the area. --- spec/unit/type/file_spec.rb | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/spec/unit/type/file_spec.rb b/spec/unit/type/file_spec.rb index 51c27c0e6..db0fa9f34 100755 --- a/spec/unit/type/file_spec.rb +++ b/spec/unit/type/file_spec.rb @@ -194,6 +194,23 @@ describe Puppet::Type.type(:file) do file = Puppet::Type::File.new(:path => "/") file[:path].should == "/" end + + it "should accept a double-slash at the start of the path" do + expect { + file = Puppet::Type::File.new(:path => "//tmp/xxx") + # REVISIT: This should be wrong, later. See the next test. + # --daniel 2011-01-31 + file[:path].should == '/tmp/xxx' + }.should_not raise_error + end + + # REVISIT: This is pending, because I don't want to try and audit the + # entire codebase to make sure we get this right. POSIX treats two (and + # exactly two) '/' characters at the start of the path specially. + # + # See sections 3.2 and 4.11, which allow DomainOS to be all special like + # and still have the POSIX branding and all. --daniel 2011-01-31 + it "should preserve the double-slash at the start of the path" end describe "on Microsoft Windows systems" do -- cgit