Skip to content

Conversation

@riichard
Copy link
Contributor

  • Contributing guide missed the npm build step when setting up the repository.
  • Added the suggestion to use PHP's built in webserver for testing, next to setting up with the LAMP. PHP is by default installed on OSX.

@nathanhammond
Copy link

Heads up: php -S didn't work for me when I was setting it up just a few days ago. (Mac OS X, 10.10)

@riichard
Copy link
Contributor Author

Which port did you use?

On Friday, August 14, 2015, Nathan Hammond notifications@github.com wrote:

Heads up: php -S didn't work for me when I was setting it up just a few
days ago. (Mac OS X, 10.10)


Reply to this email directly or view it on GitHub
#2537 (comment).

README.md Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I shouldn't have committed this change. There is nothing different compared
to before.

I initially thought about altering the Mac installation description for
Lamp, because PHP was already installed on OS X.

Then I thought it would be better just to insert a quick tip for using PHPs
build server if you're on OS X or already have OS X installed.
Because maybe some people still want to use LAMP on OS X.

On Monday, August 17, 2015, Michał Gołębiowski notifications@github.com
wrote:

In README.md
#2537 (comment):

Why this change?


Reply to this email directly or view it on GitHub
https://github.com/jquery/jquery/pull/2537/files#r37152489.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we still recommend to use those, for Windows, sure, but for the Linux or Mac? If it is a Linux user, their definitely know how to install php and http-server. If it is a Mac user, their already have apache and php in the system.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They still need to be configured, even on a Mac and it's not that easy.

The best solution would be to fix #1755 but it needs some effort.

@mgol
Copy link
Member

mgol commented Sep 8, 2015

@riichard Did you see our comments? The standalone PHP server won't work and the Mac info was just swapped so these changes should be reverted. This will get README.md back to the state it was in, the only change will be in CONTRIBUTING.md. Would you like to apply these changes? Or do you have any other suggestions?

@riichard
Copy link
Contributor Author

@mzgol I see your comments, the tests worked fine with php running on my machine but I guess there are exceptions and differences to apache. It's best to leave that README.md suggestion out then.

I would still like to apply the changes to CONTRIBUTING.md.

@mgol
Copy link
Member

mgol commented Sep 11, 2015

@mzgol I see your comments, the tests worked fine with php running on my machine

Did you run the whole suite? I remember I used to have a lot of issues with the standalone server, although now I see only 4 of them (I tried on OS X 10.11 GM Candidate, PHP 5.5.27):
screen shot 2015-09-11 at 20 37 51

If my memory is fine, though, it might work worse on older versions and even then the test suite still doesn't pass completely. So I think this advice would be risky in general.

I would still like to apply the changes to CONTRIBUTING.md.

Sure. :) Just revert the other changes and we'll land this one.

@riichard
Copy link
Contributor Author

It was a challenge for me to revert that commit from github, but I got it done. The PHP server suggestion commit is removed.

The only commit left fixes CONTRIBUTING.md's missing 'npm run build' step.

@mgol
Copy link
Member

mgol commented Oct 7, 2015

LGTM.

@mgol mgol self-assigned this Oct 7, 2015
@mgol mgol added Build and removed Needs info labels Oct 7, 2015
@mgol mgol added this to the 3.0.0 milestone Oct 7, 2015
@markelog
Copy link
Member

markelog commented Oct 8, 2015

LGTM

@timmywil timmywil closed this in 735dea3 Oct 12, 2015
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Development

Successfully merging this pull request may close these issues.

6 participants