In the 6.x-1.7 release, the apachesolr module purposely introduced a .gitignore file that excludes all the project-required SolrPhpClient library files.
This creates many unexpected issues on projects that are deployed via Git (which an ever-increasing number are), as anytime the apachesolr module is enabled, it gives an error saying the SolrPhpClient is missing, despite being appearing on the development codebase to be installed correctly.
Rather than forcing Git-savvy developers to 'hack' the module to remove the .gitignore file, perhaps it can be deleted from the project and prevent further head-scratching from other devs? (Or, at the very least, explain the reasoning behind including this file?)
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 1905392-2-remove-gitignore-3.x.patch | 333 bytes | dstol |
| #1 | 1905392-1-remove-gitignore.patch | 333 bytes | dstol |
Comments
Comment #1
dstolSpent way too much time debugging this today.
Comment #2
dstolHere's a 3.x patch too
Comment #3
nick_vhThis is actually only valid for the 6.x-1.x branch. I don't see any direct reason why you should remove this. When you download this module, is the gitignore included with the tar.gz/zip?
Comment #4
dstolThe .gitignore is included in the tar.gz.
This is what ended up happening to me today:
Spent about an hour or so scratching my head until I randomly did a git status --ignored, which brought me here.
Comment #5
nick_vhThat sounds more like a packaging failure of drupal.org, it should never include the .gitignore? can you check if there is already an issue for that on drupal.org?
Comment #6
nick_vhThat sounds more like a packaging failure of drupal.org, it should never include the .gitignore? can you check if there is already an issue for that on drupal.org?
Comment #7
dstolI'm nearly 100% sure d.o packaging will always include a .gitignore that is in a repo. Core used to do ship with a .gitignore, which was reverted for similar reasons. #1170538: Rename core .gitignore file to example.gitignore and add explanatory comments
Another way to go about it (and I'm not 100% sure if this is supported) but you could add a .gitattributes that looks like:
.gitignore export-ignoreComment #8
pwolanin commentedI don't recall any reason for adding in the 1st place, so removing it for now.
Comment #9
dstolThanks Peter!