-
-
Notifications
You must be signed in to change notification settings - Fork 374
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
Speed up install by disabling RDOC generation #13
Comments
Who needs rdoc/ri generation on a server? Especially on an automated server? Skipping rdoc/ri generation would be fantastic. |
Agreed, I hate that as well (rubygems/rubygems#42). Only thing I'm iffy on is going against the rubygems default (principal of least surprise), even if it's kinda lame. Besides, it's possible that the cookbook could be used for development workstations as well. What do you both think about an attribue, something like:
which could be overridden to To be honest, I forgot about this build delay because sooner or later I drop in a |
I think it is a good idea, but I think the default should be false because it is the most common option for most automated install environments. |
I don't think my arm needed too much twisting there. Will do (make |
Thanks! |
+1 |
So, it looks like the
|
Hi Fletcher, I think we are talking about different things. You are talking about the 'gem_package' definition, while I'm talking about installing Ruby through RVM. I believe that gem_package won't generated RDoc, but while installing RVM Ruby and watching 'top', I've noticed that 100% of the CPU was being used for generating the docs for the initial/default gems installed by RVM. I talked with Waynee and told him that we would like to avoid changing gemrc for disabling RDoc generation for the initial gems while installing RVM Ruby. He told me that we could add 'export rvm_gem_options="--no-rdoc --no-ri"' to rvmrc. What do you think about this option? |
Great, I saw your patch to RVM. I'll get this added in the next couple of days, thanks for your help! |
Done! Looks okay? |
Yes, it looks ok. I just didn't understand why using "enable"/"disable" instead of true/false. Another approach also would be something like:
What do you think about it? |
I would at least name it I might also tend to name it in the positive with a zero/null/empty default, as the following examples:
|
How does this look? I agree, that feels better. The reason for those crazy "enable"/"disable" values is because I didn't realize you could use boolean value in attributes and the |
+1 |
Awesome! :) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I've noticed that a lot of CPU time and memory is used by a long time in:
./ruby -rpurelib.rb ./bin/rdoc --all --ri --op .ext/rdoc .
Maybe it would be great to disable RDOC generation from the beggining for make the install process faster... What do you think?
The text was updated successfully, but these errors were encountered: