Bugs item #29145, was opened at 2011-04-23 04:36
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29145&group_id=126
Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Lars Christensen (larsch)
Assigned to: James Tucker (raggi)
Summary: Dynamically generated GemSpec.files ends up empty
Initial Comment:
Prawn's gemspec:
spec.files = Dir.glob("{examples,lib,spec,data}/**/**/*") +
["Rakefile", "prawn.gemspec"]
With pristine 1.9.2-p180 on Windows (all good):
C:\>gem --version
1.5.2
C:\>gem install prawn
...
specifications/prawn-0.11.1.gemspec:
s.files = ["examples/example_helper.rb","
examples/bounding_box/stretched_nesting.rb",
"examples/bounding_box/bounding_boxes.rb",
"examples/bounding_box/indentation.rb", ... ]
With upgrades rubygems (s.files misses files):
C:\>gem update --system
...
C:\>gem --version
1.7.2
C:\>gem install prawn
...
specifications/prawn-0.11.1.gemspec:
s.files = ["HACKING", "README", "LICENSE", "COPYING"]
All .rb files are missing in .files.
Currently ocra (http://ocra.rubyforge.org/) uses .files to find the files that
are included in a gem, and hence fails miserably when they are not actually
listen in the .gemspec file.
----------------------------------------------------------------------
Comment By: Ryan Davis (zenspider)
Date: 2011-06-07 16:50
Message:
Hi!
Believe it or not, we're moving to github's issue tracker! The
pressure to move has been loud and clear, but for the longest time
it didn't support the way we worked. Now that it has freeform
labels it can support our workflow adequately. There is just one
problem: Your bug is here and we don't want to lose you!
What we'd like you to do is fairly painless and should only take a
few minutes:
Please file the _exact_ same ticket on github and provide a link
back to this crufty old ticket so we can refer to any previous
discussion that occurred. Once the new ticket is made, put a
forwarding link to it here and close this ticket out. In a couple
weeks, we'll track down the old tickets that are still open and
decide what to do with them.
We could have done this fairly automatically, but we really want
you to do it so you're attached to the ticket and we can still
communicate with you and keep a record of it.
https://github.com/rubygems/rubygems/issues
Thanks,
The RubyGems Team
----------------------------------------------------------------------
Comment By: Luis Lavena (luislavena)
Date: 2011-05-23 17:47
Message:
I've bring this topic to RubyGems devel list before:
http://rubyforge.org/pipermail/rubygems-developers/2011-May/006539.html
Like you I depend on that functionality.
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29145&group_id=126
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
