Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Add MacPorts support. #681

vvakame opened this Issue Nov 1, 2012 · 3 comments


None yet
3 participants

vvakame commented Nov 1, 2012

I'm MacPorts user. but Yeoman focus to only HomeBrew.

I'm written a patch.
What do you think?

I found a bug. error message for optipng are always shown.
My patch are fix it together.

thank you for talk about Yeoman in Chrome Tech Talk Night #4 at Google Japan.
I'm GAE/J and Dart or TypeScript man :)


sindresorhus commented Nov 3, 2012

Seeing as Homebrew is the "de facto" OS X package manager these days and it can co-exist with MacPorts I don't really see the point. If you insist on only using MacPorts, you can easily enough go through the manual install guide without the audit script.

I found a bug. error message for optipng are always shown.

Separate PR and we'll merge right away :)

vvakame commented Nov 4, 2012

umm... Share of HomeBrew vs MacPorts is 50:50 around me.
Usually not install two more package manager.
I think checker script is very important for new comer.

by the way, Should I write a instruction for MacPorts user that likes debian? ( #461 )

Separate PR and we'll merge right away :)

this issue were fixed by this commit already. :)


addyosmani commented Nov 14, 2012

Wontfix. Yeoman is changing the way users install us in 1.0 to be a lot more simplified with a thinner dependency tree. As a part of this, we want be looking at MacPorts support. Sorry!

@addyosmani addyosmani closed this Nov 14, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment