Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add spm support #1630

Closed
wants to merge 1 commit into from
Closed

add spm support #1630

wants to merge 1 commit into from

Conversation

afc163
Copy link

@afc163 afc163 commented May 7, 2014

@jashkenas
Copy link
Owner

Thanks, but no thanks...

@michaelficarra
Copy link
Collaborator

@afc163: See jashkenas/coffeescript#2395.

@jdalton
Copy link
Contributor

jdalton commented May 7, 2014

I had a similar concern over the added dot file too. See lodash/543.

@davidchambers
Copy link
Contributor

This really is becoming ridiculous. Three JavaScript package managers are not enough, apparently?

@michaelficarra
Copy link
Collaborator

Hey, I'm all for more choice, but your package manager is just plain broken if it requires a package-manager-named key in package.json. All meta-information should be generically specified. See all of the other keys in package.json as an example of this.

@jdalton
Copy link
Contributor

jdalton commented May 7, 2014

Hey, I'm all for more choice, but your package manager is just plain broken if it requires a package-manager-named key in package.json.

I'd rather have it in the package.json instead of in lots of separate files.
This is why we can't have nice things! No one agrees on anything :P

@michaelficarra
Copy link
Collaborator

Me too! All meta-information can be in package.json. But not namespaced for your package manager, that's ridiculous.

@jdalton
Copy link
Contributor

jdalton commented May 7, 2014

But not namespaced for your package manager, that's ridiculous.

Ya though namespacing avoid collisions. I don't mind it (it's a bit of duplicate info but when implementations can't agree namespacing fits well)

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

Successfully merging this pull request may close these issues.

5 participants