pkgsync(8) [debian man page]

PKGSYNC(8)						      System Manager's Manual							PKGSYNC(8)

NAME

       pkgsync - Automated package synchronization tool

SYNOPSIS

       pkgsync

DESCRIPTION

       pkgsync	is  a  tool  for  keeping multiple machines reasonably similar and clean. Packages can either be in a `must be installed', `may be
       installed' or `must not be installed' list (which is presumed to be distributed separately  using  a  tool  such  as  rdist  or	cfengine).
       pkgsync	will  take care of meeting the demands put down in the lists, and then removing everything that is not in the `must' or `may' list
       and is not necessary for their operations (as determined by aptitude).

OPTIONS

       -h, --help
	      Print a short help text and exit.

       -s, --simulate
	      Do everything as usual, but put aptitude in simulation mode, causing it to never do any changes (except update and autoclean,  which
	      should both be harmless) to your system. This is especially useful on a new system to make sure pkgsync behaves as expected.

	      Note  that aptitude prints out its intended actions _before_ running the conflict resolver. If there's a conflict somewhere, chances
	      are that the results on your system will be different from what aptitude prints out.

       -k, --keep-unused
	      Instruct aptitude to not remove cruft (ie. unused packages); this is morally equivalent to having an "*" entry in mayhave.

       -d, --dpkg-glob
	      When encountering a wildcard pattern, pkgsync tries to `un-glob' it.  Traditionally, this was done using dpkg -- however,  in  later
	      versions	one can use aptitude instead. Using aptitude is a little slower, but the syntax is a lot more flexible, supporting regular
	      expressions and various searches on fields. Giving --dpkg-glob makes pkgsync use dpkg, which is not very useful except for backwards
	      compatibility.

       -a, --aptitude-glob
	      Use aptitude's globbing instead of dpkg's globbing (see above). This option is the default.

SEE ALSO

       /usr/share/doc/pkgsync/README.Debian (complete tutorial and reference documentation)

AUTHOR

       pkgsync is Copyright 2004-2007 Steinar H. Gunderson <sgunderson@bigfoot.com>.

																	PKGSYNC(8)

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)