Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

aptitude-run-state-bundle(1) [linux man page]

APTITUDE-RUN-ST(1)					      Command-line reference						APTITUDE-RUN-ST(1)

NAME

       aptitude-run-state-bundle - unpack an aptitude state bundle and invoke aptitude on it

SYNOPSIS

       aptitude-run-state-bundle [<options>...] <input-file> [<program> [<arguments>...]]

DESCRIPTION

       aptitude-run-state-bundle unpacks the given aptitude state bundle created by aptitude-create-state-bundle(1) to a temporary directory,
       invokes <program> on it with the supplied <arguments>, and removes the temporary directory afterwards. If <program> is not supplied, it
       defaults to aptitude(8).

OPTIONS

       The following options may occur on the command-line before the input file. Options following the input file are presumed to be arguments to
       aptitude.

       --append-args
	   Place the options that give the location of the state bundle at the end of the command line when invoking <program>, rather than at the
	   beginning (the default is to place options at the beginning).

       --help
	   Display a brief usage summary.

       --prepend-args
	   Place the options that give the location of the state bundle at the beginning of the command line when invoking <program>, overriding
	   any previous --append-args (the default is to place options at the beginning).

       --no-clean
	   Do not remove the unpacked state directory after running aptitude. You might want to use this if, for instance, you are debugging a
	   problem that appears when aptitude's state file is modified. When aptitude finishes running, the name of the state directory will be
	   printed so that you can access it in the future.

	   This option is enabled automatically by --statedir.

       --really-clean
	   Delete the state directory after running aptitude, even if --no-clean or --statedir was supplied.

       --statedir
	   Instead of treating the input file as a state bundle, treat it as an unpacked state bundle. For instance, you can use this to access
	   the state directory that was created by a prior run with --no-clean.

       --unpack
	   Unpack the input file to a temporary directory, but don't actually run aptitude.

SEE ALSO

       aptitude-create-state-bundle(1), aptitude(8), apt(8)

AUTHOR

       Daniel Burrows <dburrows@debian.org>
	   Author.

COPYRIGHT

       Copyright 2007 Daniel Burrows.

       This manual page is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published
       by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

       This manual page is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
       MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

       You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation,
       Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

aptitude-run-state-bundle 0.6.					    08/08/2011							APTITUDE-RUN-ST(1)

Check Out this Related Man Page

BUNDLE-PACKAGE(1)														 BUNDLE-PACKAGE(1)

NAME

       bundle-package - Package your needed .gem files into your application

SYNOPSIS

       bundle package

DESCRIPTION

       Copy  all  of  the  .gem files needed to run the application into the vendor/cache directory. In the future, when running bundle install(1)
       bundle-install.1.html, use the gems in the cache in preference to the ones on rubygems.org.

GIT AND PATH GEMS

       Since Bundler 1.2, the bundle package command can also package :git and :path dependencies besides .gem files. This needs to be	explicitly
       enabled via the --all option. Once used, the --all option will be remembered.

REMOTE FETCHING

       By  default,  if you simply run bundle install(1) bundle-install.1.html after running bundle package(1) bundle-package.1.html, bundler will
       still connect to rubygems.org to check whether a platform-specific gem exists for any of the gems in vendor/cache.

       For instance, consider this Gemfile(5):

	   source "https://rubygems.org"

	   gem "nokogiri"

       If you run bundle package under C Ruby, bundler will retrieve the version of nokogiri for the "ruby" platform. If you deploy to	JRuby  and
       run bundle install, bundler is forced to check to see whether a "java" platformed nokogiri exists.

       Even  though  the nokogiri gem for the Ruby platform is technically acceptable on JRuby, it actually has a C extension that does not run on
       JRuby. As a result, bundler will, by default, still connect to rubygems.org to check whether it has a version of one of your gems more spe-
       cific to your platform.

       This  problem is also not just limited to the "java" platform. A similar (common) problem can happen when developing on Windows and deploy-
       ing to Linux, or even when developing on OSX and deploying to Linux.

       If you know for sure that the gems packaged in vendor/cache are appropriate for the platform you are on, you can run bundle install --local
       to skip checking for more appropriate gems, and just use the ones in vendor/cache.

       One  way to be sure that you have the right platformed versions of all your gems is to run bundle package on an identical machine and check
       in the gems. For instance, you can run bundle package on an identical staging box during your  staging  process,  and  check  in  the  ven-
       dor/cache before deploying to production.

								    March 2013							 BUNDLE-PACKAGE(1)
Man Page