Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=588474 --- Comment #12 from Matthew Kent <mkent@xxxxxxxxxxxx> 2010-05-13 01:57:14 EDT --- (In reply to comment #11) > I'm reluctant to split the package as then the gem will calim to be installed, > but won't provide the same set of files as the upstream gem. While this is true I think there is merit to splitting them up: 1) rdoc/ri - some of my rubygem -doc packages are 2x the size of the main page due to all the rdoc/ri generation. There are far more files as well - rubygem-merb-core has 128 files while the -doc has 2320! And I don't find much use for rdoc content on every server I manage. 2) cruft - I can't count the number of gems that I've looked at that ship Rakefiles with long lists of development dependencies, random scripts, files used for development, entire copies of the projects website, etc. Cruft that might get removed anyway if this was a standard package installation. Of course it's not being removed - just tucked away in a subpackage. 3) functionality - With splitting them up users can at least be assured that what's shipped in the primary package should function, while getting the random Rakefiles, examples, test suites and such working would require many more dependencies to package/track. Plus I don't think it's to much to say "yum install rubygem-rubyzip*" gives you everything the gem install would. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review