." generated with Ronn/v0.7.3 ." github.com/rtomayko/ronn/tree/0.7.3 . .TH “BUNDLE-GEM” “1” “October 2015” “” “” . .SH “NAME” fBbundle-gemfR - Generate a project skeleton for creating a rubygem . .SH “SYNOPSIS” fBbundle gemfR fIGEM_NAMEfR fIOPTIONSfR . .SH “DESCRIPTION” Generates a directory named fBGEM_NAMEfR with a fBRakefilefR, fBGEM_NAME.gemspecfR, and other supporting files and directories that can be used to develop a rubygem with that name. . .P Run fBrake -TfR in the resulting project for a list of Rake tasks that can used to test and publish the gem to rubygems.org. . .P The generated project skeleton can be customized with OPTIONS, as explained below. Note that these options can also be specified via Bundler's global configuration file using the following names: . .IP “(bu” 4 fBgem.cocfR . .IP “(bu” 4 fBgem.mitfR . .IP “(bu” 4 fBgem.testfR . .IP “” 0 . .SH “OPTIONS” . .TP fB-bfR or fB--binfR Specify that Bundler should create a binary (as fBexe/GEM_NAMEfR) in the generated rubygem project. This binary will also be added to the fBGEM_NAME.gemspecfR manifest. This behavior is disabled by default. . .TP fB--no-binfR Do not create a binary (overrides fB--binfR specified in the global config). . .TP fB--cocfR Add a fBCODE_OF_CONDUCT.mdfR file to the root of the generated project. If this option is unspecified, an interactive prompt will be displayed and the answer will be saved in Bundler's global config for future fBbundle gemfR use. . .TP fB--no-cocfR Do not create a fBCODE_OF_CONDUCT.mdfR (overrides fB--cocfR specified in the global config). . .TP fB--extfR Add boilerplate for C extension code to the generated project. This behavior is disabled by default. . .TP fB--no-extfR Do not add C extension code (overrides fB--extfR specified in the global config). . .TP fB--mitfR Add an MIT license to a fBLICENSE.txtfR file in the root of the generated project. Your name from the global git config is used for the copyright statement. If this option is unspecified, an interactive prompt will be displayed and the answer will be saved in Bundler's global config for future fBbundle gemfR use. . .TP fB--no-mitfR Do not create a fBLICENSE.txtfR (overrides fB--mitfR specified in the global config). . .TP fB-tfR, fB--test=minitestfR, fB--test=rspecfR Specify the test framework that Bundler should use when generating the project. Acceptable values are fBminitestfR and fBrspecfR. The fBGEM_NAME.gemspecfR will be configured and a skeleton test/spec directory will be created based on this option. If this option is unspecified, an interactive prompt will be displayed and the answer will be saved in Bundler's global config for future fBbundle gemfR use. . .TP fB-efR, fB--edit[=EDITOR]fR Open the resulting GEM_NAME.gemspec in EDITOR, or the default editor if not specified. The default is fB$BUNDLER_EDITORfR, fB$VISUALfR, or fB$EDITORfR. . .SH “SEE ALSO” . .IP “(bu” 4 bundle-config(1) . .IP “” 0