FM / man1

/opt/alt/ruby26/share/man/man1

Name	Size	Mode	Actions
bundle-add.1	1327	0644	edit dl rm
bundle-binstubs.1	1730	0644	edit dl rm
bundle-check.1	966	0644	edit dl rm
bundle-clean.1	604	0644	edit dl rm
bundle-config.1	21422	0644	edit dl rm
bundle-doctor.1	1165	0644	edit dl rm
bundle-exec.1	6761	0644	edit dl rm
bundle-gem.1	3244	0644	edit dl rm
bundle-info.1	449	0644	edit dl rm
bundle-init.1	1078	0644	edit dl rm
bundle-inject.1	738	0644	edit dl rm
bundle-install.1	16774	0644	edit dl rm
bundle-list.1	871	0644	edit dl rm
bundle-lock.1	3191	0644	edit dl rm
bundle-open.1	581	0644	edit dl rm
bundle-outdated.1	3814	0644	edit dl rm
bundle-package.1	3326	0644	edit dl rm
bundle-platform.1	1340	0644	edit dl rm
bundle-pristine.1	1678	0644	edit dl rm
bundle-remove.1	849	0644	edit dl rm
bundle-show.1	690	0644	edit dl rm
bundle-update.1	13917	0644	edit dl rm
bundle-viz.1	1105	0644	edit dl rm
bundle.1	3505	0644	edit dl rm
erb.1	3326	0644	edit dl rm
irb.1	3446	0644	edit dl rm
ri.1	5347	0644	edit dl rm
ruby.1	19079	0644	edit dl rm

Edit: /opt/alt/ruby26/share/man/man1/bundle-package.1 (3326B)

.\" generated with Ronn/v0.7.3
.\" http://github.com/rtomayko/ronn/tree/0.7.3
.
.TH "BUNDLE\-PACKAGE" "1" "November 2018" "" ""
.
.SH "NAME"
\fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application
.
.SH "SYNOPSIS"
\fBbundle package\fR
.
.SH "DESCRIPTION"
Copy all of the \fB\.gem\fR files needed to run the application into the \fBvendor/cache\fR directory\. In the future, when running [bundle install(1)][bundle\-install], use the gems in the cache in preference to the ones on \fBrubygems\.org\fR\.
.
.SH "GIT AND PATH GEMS"
Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR and \fB:path\fR dependencies besides \.gem files\. This needs to be explicitly enabled via the \fB\-\-all\fR option\. Once used, the \fB\-\-all\fR option will be remembered\.
.
.SH "SUPPORT FOR MULTIPLE PLATFORMS"
When using gems that have different packages for different platforms, Bundler 1\.8 and newer support caching of gems for other platforms where the Gemfile has been resolved (i\.e\. present in the lockfile) in \fBvendor/cache\fR\. This needs to be enabled via the \fB\-\-all\-platforms\fR option\. This setting will be remembered in your local bundler configuration\.
.
.SH "REMOTE FETCHING"
By default, if you run \fBbundle install(1)\fR](bundle\-install\.1\.html) after running bundle package(1) \fIbundle\-package\.1\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
.
.P
For instance, consider this Gemfile(5):
.
.IP "" 4
.
.nf

source "https://rubygems\.org"

gem "nokogiri"
.
.fi
.
.IP "" 0
.
.P
If you run \fBbundle package\fR under C Ruby, bundler will retrieve the version of \fBnokogiri\fR for the \fB"ruby"\fR platform\. If you deploy to JRuby and run \fBbundle install\fR, bundler is forced to check to see whether a \fB"java"\fR platformed \fBnokogiri\fR exists\.
.
.P
Even though the \fBnokogiri\fR gem for the Ruby platform is \fItechnically\fR acceptable on JRuby, it has a C extension that does not run on JRuby\. As a result, bundler will, by default, still connect to \fBrubygems\.org\fR to check whether it has a version of one of your gems more specific to your platform\.
.
.P
This problem is also not limited to the \fB"java"\fR platform\. A similar (common) problem can happen when developing on Windows and deploying to Linux, or even when developing on OSX and deploying to Linux\.
.
.P
If you know for sure that the gems packaged in \fBvendor/cache\fR are appropriate for the platform you are on, you can run \fBbundle install \-\-local\fR to skip checking for more appropriate gems, and use the ones in \fBvendor/cache\fR\.
.
.P
One way to be sure that you have the right platformed versions of all your gems is to run \fBbundle package\fR on an identical machine and check in the gems\. For instance, you can run \fBbundle package\fR on an identical staging box during your staging process, and check in the \fBvendor/cache\fR before deploying to production\.
.
.P
By default, bundle package(1) \fIbundle\-package\.1\.html\fR fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\.

cmd: