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(1)																 BUNDLE(1)

NAME

       bundle - Ruby Dependency Management

SYNOPSIS

       bundle COMMAND [--no-color] [--verbose] [ARGS]

DESCRIPTION

       Bundler manages an application's dependencies through its entire life across many machines systematically and repeatably.

       See  the  bundler website http://gembundler.com for information on getting started, and Gemfile(5) for more information on the Gemfile for-
       mat.

OPTIONS

       --no-color
	      Prints all output without color

       --verbose
	      Prints out additional logging information

BUNDLE COMMANDS

       We divide bundle subcommands into primary commands and utilities.

PRIMARY COMMANDS

       bundle install(1) bundle-install.1.html
	      Install the gems specified by the Gemfile or Gemfile.lock

       bundle update(1) bundle-update.1.html
	      Update dependencies to their latest versions

       bundle package(1) bundle-package.1.html
	      Package the .gem files required by your application into the vendor/cache directory

       bundle exec(1) bundle-exec.1.html
	      Execute a script in the context of the current bundle

       bundle config(1) bundle-config.1.html
	      Specify and read configuration options for bundler

UTILITIES

       bundle check(1)
	      Determine whether the requirements for your application are installed and available to bundler

       bundle list(1)
	      Show all of the gems in the current bundle

       bundle show(1)
	      Show the source location of a particular gem in the bundle

       bundle outdated(1)
	      Show all of the outdated gems in the current bundle

       bundle console(1)
	      Start an IRB session in the context of the current bundle

       bundle open(1)
	      Open an installed gem in the editor

       bundle viz(1)
	      Generate a visual representation of your dependencies

       bundle init(1)
	      Generate a simple Gemfile, placed in the current directory

       bundle gem(1)
	      Create a simple gem, suitable for development with bundler

OBSOLETE

       These commands are obsolete and should no longer be used

       o   bundle lock(1)

       o   bundle unlock(1)

       o   bundle cache(1)

								     June 2012								 BUNDLE(1)
Man Page