Handle linux paths on windows.

[dsherret]

For #14. I wouldn't be surprised if someone were depending on the previous behaviour, so this seems like a breaking change in behaviour.

This means it will work the same on linux and windows.

[e-cloud]

@jonschlinkert could you have a review?

[jonschlinkert]

thanks for the ping, and sorry for the delay. I get heartburn from path issues, especially when they are Windows related, and even more so when they are for Linux on Windows (jk!).

so this seems like a breaking change in behaviour.

Is this always desired behavior though? Should we expose an option to unixify the path root?

[dsherret]

@jonschlinkert I think it would be easiest if people provide that by doing the following:

toAbsoluteGlob("**/*.txt", { root: path.resolve("/") }));

That doesn't require an extra option. What do you think?

Side note: In nodejs it seems that / will be the current drive letter. So I can do fs.readFileSync("/somefile.txt", "utf8") and it will read the file at C:\somefile.txt. I believe the main problem would be if someone provided / previously for root and was passing that glob to some other code that was relying on it having a drive letter.