Only include Manifest.txt in gemspec if it is present #45

Closed
wants to merge 1 commit into
from

Projects

None yet

4 participants

@ragaskar

Since Manifest.txt is .gitignore-d, if you track the git repo using bundler, bundler will complain that the gemspec is asking for Manifest.txt but it can't find it. IE:

ragaskar@unicorn-vengeance: ~/workspace/testme$ bundle
Using builder (3.0.0) 
Using ci_reporter (1.6.5) from git://github.com/ragaskar/ci_reporter.git (at master) 
ci_reporter at /Users/ragaskar/.rvm/gems/ruby-1.9.2-p290@ci_reporter/bundler/gems/ci_reporter-af8674c7bddc did not have a valid gemspec.
This prevents bundler from installing bins or native extensions, but that may not affect its functionality.
The validation message from Rubygems was:
  ["Manifest.txt"] are not files

Using bundler (1.0.21) 
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.

This minor patch to gemspec fixes the problem.

Thanks for ci_reporter!

@dcuddeback

This is affecting me too. I'm currently tracking HEAD because of the Errno::ENAMETOOLONG error bug. Any chance of applying this patch?

@dgilperez

+1

@nicksieger nicksieger added a commit that closed this pull request Jan 28, 2012
@nicksieger nicksieger Add manifest to source control
fixes #45.
8639695
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment