tag:blogger.com,1999:blog-581197352358126527.post1286681231939554141..comments2024-03-28T00:32:25.959-07:00Comments on japh(r) by Chris Strom: Dart Pub for Local DevelopmentAnonymoushttp://www.blogger.com/profile/00135361916531185929noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-581197352358126527.post-46535077247769669482012-06-06T15:21:42.466-07:002012-06-06T15:21:42.466-07:00My concern is only the pubspec file. I agree that ...My concern is only the pubspec file. I agree that it's a minor thing, but I worry that I'll end up checking in a pubspec file modified for local development. I can see something like a pubspec change getting lost in the wash of a large commit.Anonymoushttps://www.blogger.com/profile/00135361916531185929noreply@blogger.comtag:blogger.com,1999:blog-581197352358126527.post-47540351706859940362012-06-06T14:40:31.079-07:002012-06-06T14:40:31.079-07:00My expectation is that you'd .gitignore (or th...My expectation is that you'd .gitignore (or the equivalent) your "packages" directory so you don't have to worry about cleaning it up before checking it in. Would that address your worry?Bob Nystromhttps://www.blogger.com/profile/03425688691695561816noreply@blogger.comtag:blogger.com,1999:blog-581197352358126527.post-43792144152953614892012-06-04T13:27:37.731-07:002012-06-04T13:27:37.731-07:00There's a page now: http://www.dartlang.org/do...There's a page now: http://www.dartlang.org/docs/pub-package-manager/Khttps://www.blogger.com/profile/15840374656223298646noreply@blogger.comtag:blogger.com,1999:blog-581197352358126527.post-10298488127926180602012-05-31T04:56:48.426-07:002012-05-31T04:56:48.426-07:00Nice! Built-in support for sym-link development is...Nice! Built-in support for sym-link development is gonna be big. Really exciting.<br /><br />I slightly prefer the npm-link approach. Both are two step processes — npm link once in the repo + once in the target project, while pub would be edit pubspec + pub install / update. The main benefit of the former is that it leaves no residual to be cleaned up before committing changes to SCM. Also, both operations are shell instead of one file edit + one shell.Anonymoushttps://www.blogger.com/profile/00135361916531185929noreply@blogger.comtag:blogger.com,1999:blog-581197352358126527.post-59183391962741577812012-05-30T13:08:47.002-07:002012-05-30T13:08:47.002-07:00Thanks for trying out pub and writing down your th...Thanks for trying out pub and writing down your thoughts. This feedback is immeasurably helpful.<br /><br />"The invaluable benefit of this approach is that any changes made to the linked package can be immediately committed without the intermediate step of copying them into a separate repository."<br /><br />This is actually a use case we intend to support directly in pub. What you're doing here (manually adding a symlink in your packages dir) is also valid, but is a pain to do manually.<br /><br />Instead, what we plan to support is file path sources. So in your pubspec, you could have something like:<br /><br />dependencies:<br /> foo:<br /> path: ~/path/to/foo<br /><br />With this, when you do a pub install, it will just create a symlink from ~/path/to/foo to foo in your packages directory. In other words, it will do exactly what you're doing manually here.Bob Nystromhttps://www.blogger.com/profile/03425688691695561816noreply@blogger.com