Exclude .gitignore files from the release tarballs
Description
Gliffy Diagrams
Activity
Show:
Jordan Sissel January 23, 2015 at 10:11 PM
Also noted that 1.5.x uses the same build process.
Jordan Sissel January 23, 2015 at 10:09 PM
I just built from master a tarball:
There is no more .gitignore files in the tar.gz releases.
Jordan Sissel January 23, 2015 at 10:08 PM
wow I had no idea so many bizarre things that were not git used .gitignore. This is confusing and quite annoying.
Tim Bunce June 16, 2014 at 4:30 AM
Here's an example where the folks developing the thread_safe gem come to the same conclusion.
Fixed
Details
Details
Assignee
Jordan SisselReporter
Tim BunceFix versions
Affects versions
Created June 16, 2014 at 2:02 AM
Updated January 23, 2015 at 10:11 PM
Resolved January 23, 2015 at 10:09 PM
and (and my own recent pain) were caused by .gitignore files included in the logstash 1.4.x releases.
My reading of those two cases is that they were resolved by the user removing one or more .gitignore files themselves.
Others are likely to fall into this hard-to-debug bear trap in future. The tar balls contains many .gitignore files.
I suggest that your release process be modified to exclude all .gitignore files from the releases.