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

Removed test_files from gemspec #386

Merged
merged 1 commit into from
Jul 2, 2015
Merged

Conversation

iainbeeston
Copy link
Contributor

I was just looking through the code installed for teaspoon, and I noticed that the /spec/dummy directory is huge. It turns out that rubygems is packaging up not only /spec/dummy, but also all the tempfiles and logfiles there at the time of packaging.

The latest consensus is that test_files shouldn't be packaged with a gem anyway (see rubygems/bundler#3207) because they're never used, so rather than filtering out /spec/dummy/log and /spec/dummy/tmp I've prevented rubygems from packing test files at all.

I was just looking through the code installed for teaspoon, and I noticed that the /spec/dummy directory is huge. It turns out that rubygems is packaging up not only /spec/dummy, but also all the tempfiles and logfiles there *at the time of packaging*.

The latest consensus is that test_files shouldn't be packaged with a gem anyway (see rubygems/bundler#3207) because they're never used, so rather than filtering out /spec/dummy/log and /spec/dummy/tmp I've prevented rubygems from packing test files at all.
@jejacks0n
Copy link
Owner

I'm cool with that.

jejacks0n added a commit that referenced this pull request Jul 2, 2015
Removed test_files from gemspec
@jejacks0n jejacks0n merged commit 76cf4ce into jejacks0n:master Jul 2, 2015
@jejacks0n
Copy link
Owner

It'll take a new release to pick that up, and I'm not sure we're ready for that just yet, but with the next release.

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

Successfully merging this pull request may close these issues.

2 participants