File Manager

X7ROOT File Manager

Current Path: /opt/alt/ruby27/share/gems/gems/bundler-2.2.24/lib/bundler/man

opt / alt / ruby27 / share / gems / gems / bundler-2.2.24 / lib / bundler / man /

ðŸ“ ..
ðŸ“„ bundle-add.1(1.45 KB)
ðŸ“„ bundle-add.1.ronn(1.22 KB)
ðŸ“„ bundle-binstubs.1(1.57 KB)
ðŸ“„ bundle-binstubs.1.ronn(1.38 KB)
ðŸ“„ bundle-cache.1(3.19 KB)
ðŸ“„ bundle-cache.1.ronn(2.87 KB)
ðŸ“„ bundle-check.1(962 B)
ðŸ“„ bundle-check.1.ronn(857 B)
ðŸ“„ bundle-clean.1(600 B)
ðŸ“„ bundle-clean.1.ronn(484 B)
ðŸ“„ bundle-config.1(20.92 KB)
ðŸ“„ bundle-config.1.ronn(18.54 KB)
ðŸ“„ bundle-doctor.1(1.13 KB)
ðŸ“„ bundle-doctor.1.ronn(975 B)
ðŸ“„ bundle-exec.1(6.6 KB)
ðŸ“„ bundle-exec.1.ronn(5.87 KB)
ðŸ“„ bundle-gem.1(4.25 KB)
ðŸ“„ bundle-gem.1.ronn(3.79 KB)
ðŸ“„ bundle-info.1(445 B)
ðŸ“„ bundle-info.1.ronn(369 B)
ðŸ“„ bundle-init.1(1.05 KB)
ðŸ“„ bundle-init.1.ronn(939 B)
ðŸ“„ bundle-inject.1(734 B)
ðŸ“„ bundle-inject.1.ronn(597 B)
ðŸ“„ bundle-install.1(17.57 KB)
ðŸ“„ bundle-install.1.ronn(16.54 KB)
ðŸ“„ bundle-list.1(961 B)
ðŸ“„ bundle-list.1.ronn(788 B)
ðŸ“„ bundle-lock.1(3.11 KB)
ðŸ“„ bundle-lock.1.ronn(2.97 KB)
ðŸ“„ bundle-open.1(577 B)
ðŸ“„ bundle-open.1.ronn(442 B)
ðŸ“„ bundle-outdated.1(3.72 KB)
ðŸ“„ bundle-outdated.1.ronn(3.46 KB)
ðŸ“„ bundle-platform.1(1.3 KB)
ðŸ“„ bundle-platform.1.ronn(1.12 KB)
ðŸ“„ bundle-pristine.1(1.63 KB)
ðŸ“„ bundle-pristine.1.ronn(1.46 KB)
ðŸ“„ bundle-remove.1(845 B)
ðŸ“„ bundle-remove.1.ronn(730 B)
ðŸ“„ bundle-show.1(686 B)
ðŸ“„ bundle-show.1.ronn(596 B)
ðŸ“„ bundle-update.1(13.55 KB)
ðŸ“„ bundle-update.1.ronn(12.47 KB)
ðŸ“„ bundle-viz.1(1.08 KB)
ðŸ“„ bundle-viz.1.ronn(958 B)
ðŸ“„ bundle.1(3.51 KB)
ðŸ“„ bundle.1.ronn(3.07 KB)
ðŸ“„ gemfile.5(21.4 KB)
ðŸ“„ gemfile.5.ronn(19.54 KB)

Editing: bundle-pristine.1.ronn

bundle-pristine(1) -- Restores installed gems to their pristine condition
===========================================================================

## SYNOPSIS

`bundle pristine`

## DESCRIPTION

`pristine` restores the installed gems in the bundle to their pristine condition
using the local gem cache from RubyGems. For git gems, a forced checkout will be performed.

For further explanation, `bundle pristine` ignores unpacked files on disk. In other
words, this command utilizes the local `.gem` cache or the gem's git repository
as if one were installing from scratch.

Note: the Bundler gem cannot be restored to its original state with `pristine`.
One also cannot use `bundle pristine` on gems with a 'path' option in the Gemfile,
because bundler has no original copy it can restore from.

When is it practical to use `bundle pristine`?

It comes in handy when a developer is debugging a gem. `bundle pristine` is a
great way to get rid of experimental changes to a gem that one may not want.

Why use `bundle pristine` over `gem pristine --all`?

Both commands are very similar.
For context: `bundle pristine`, without arguments, cleans all gems from the lockfile.
Meanwhile, `gem pristine --all` cleans all installed gems for that Ruby version.

If a developer forgets which gems in their project they might
have been debugging, the Rubygems `gem pristine [GEMNAME]` command may be inconvenient.
One can avoid waiting for `gem pristine --all`, and instead run `bundle pristine`.

X7ROOT File Manager

Editing: bundle-pristine.1.ronn

Upload File

Create Folder