Move path ("pathos") to pkg/.

Move path ("pathos") to pkg/.

Committed: https://code.google.com/p/dart/source/detail?r=16297

[Bob Nystrom, 2012-12-18 21:25:26]

This is in preparation for putting it on pub.dartlang.org so that web_ui and
buildtool can use it. The names of the directories here are just "path", but the
name of the package itself is "pathos", which is how it will appear on
pub.dartlang.org.

In the SDK, it's going in "pkg" like the other packages do, but I expect it to
move to lib/_internal when the other packages do.

I've filtered it out so it won't appear on api.dartlang.org.

[nweiz, 2012-12-18 22:56:57]

lgtm

https://codereview.chromium.org/11647003/diff/2001/pkg/path/pubspec.yaml
File pkg/path/pubspec.yaml (right):

https://codereview.chromium.org/11647003/diff/2001/pkg/path/pubspec.yaml#newc...
pkg/path/pubspec.yaml:10: configurations-specific code is supported by Dart.
Nit: "configuration"

Also, wouldn't it be relatively easy to add a "builder" library that is
importable in the browser?

[Bob Nystrom, 2012-12-18 23:57:36]

Thanks!

https://codereview.chromium.org/11647003/diff/2001/pkg/path/pubspec.yaml
File pkg/path/pubspec.yaml (right):

https://codereview.chromium.org/11647003/diff/2001/pkg/path/pubspec.yaml#newc...
pkg/path/pubspec.yaml:10: configurations-specific code is supported by Dart.
On 2012/12/18 22:56:57, nweiz wrote:
> Nit: "configuration"
> 
> Also, wouldn't it be relatively easy to add a "builder" library that is
> importable in the browser?

Yeah, if we wanted path to not depend on dart io, that could be pulled out. But
that would mean you'd always have to do two imports to use it, which is lame.

[nweiz, 2012-12-19 00:48:46]

https://codereview.chromium.org/11647003/diff/2001/pkg/path/pubspec.yaml
File pkg/path/pubspec.yaml (right):

https://codereview.chromium.org/11647003/diff/2001/pkg/path/pubspec.yaml#newc...
pkg/path/pubspec.yaml:10: configurations-specific code is supported by Dart.
On 2012/12/18 23:57:36, Bob Nystrom wrote:
> On 2012/12/18 22:56:57, nweiz wrote:
> > Nit: "configuration"
> > 
> > Also, wouldn't it be relatively easy to add a "builder" library that is
> > importable in the browser?
> 
> Yeah, if we wanted path to not depend on dart io, that could be pulled out.
But
> that would mean you'd always have to do two imports to use it, which is lame.

Not so; we have re-exporting.

How do you envision it being used on the browser if not with a builder? There's
no context information like CWD or operating system.

[Bob Nystrom, 2012-12-19 22:32:12]

On 2012/12/19 00:48:46, nweiz wrote:
> https://codereview.chromium.org/11647003/diff/2001/pkg/path/pubspec.yaml
> File pkg/path/pubspec.yaml (right):
> 
>
https://codereview.chromium.org/11647003/diff/2001/pkg/path/pubspec.yaml#newc...
> pkg/path/pubspec.yaml:10: configurations-specific code is supported by Dart.
> On 2012/12/18 23:57:36, Bob Nystrom wrote:
> > On 2012/12/18 22:56:57, nweiz wrote:
> > > Nit: "configuration"
> > > 
> > > Also, wouldn't it be relatively easy to add a "builder" library that is
> > > importable in the browser?
> > 
> > Yeah, if we wanted path to not depend on dart io, that could be pulled out.
> But
> > that would mean you'd always have to do two imports to use it, which is
lame.
> 
> Not so; we have re-exporting.
>

True, but that still couples the importing code to a specific configuration.
 
> How do you envision it being used on the browser if not with a builder?
There's
> no context information like CWD or operating system.

I haven't put much thought into this yet, but I have a dream that I can make
URLs just another path style that this supports. On a browser, then, you could
use window.location.href as something like the cwd.