mirror of
https://github.com/fspc/dswim.git
synced 2026-09-16 08:31:39 -04:00
*** empty log message ***
This commit is contained in:
freesource
@@ -0,0 +1,49 @@
|
||||
<html><head>
|
||||
<title>swim - PREPARING YOUR INSTALLATION FOR APT
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 8<br>
|
||||
PREPARING YOUR INSTALLATION FOR APT
|
||||
|
||||
</h1>
|
||||
|
||||
<pre>usage: swim --audit
|
||||
swim --status
|
||||
swim -C</pre>
|
||||
<P>
|
||||
|
||||
If you are using <strong>apt</strong> with <strong>swim</strong>, and this
|
||||
is the first time you are using it with your installation, check your live
|
||||
installation with this major mode. This is a call to <strong>dpkg -C
|
||||
(--audit)</strong>, and will show any packages which are not properly
|
||||
configured or installed. If you get any output, make corrections. The goal
|
||||
is to get absolutely no output whatsoever because it is under these
|
||||
conditions that apt will work properly. See the <A href="ch-query.html#s-vrrm">REMOVING AN INSTALLED PACKAGE - VIRTUAL OPTIONS
|
||||
, section 9.8</A> with
|
||||
<strong>-q</strong> to remove the offending packages. You may have to
|
||||
remove the package by hand under unusual situations like when it is not
|
||||
just dependencies (see <code>-T</code>) between packages keeping the package
|
||||
from being removed perhaps due to a broken script (see
|
||||
<code>--scripts</code>). In an extreme case you could manually remove the
|
||||
entry for this package from the <em>/var/lib/dpkg/status</em> database,
|
||||
and hunt down and remove all the files associated with the package with
|
||||
<strong>swim's -l</strong> option. When you are done if you still want
|
||||
some of the packages you removed, use <strong>apt</strong> to reinstall
|
||||
them with <strong>swim's -xyz</strong> option. Also, <strong>apt</strong>
|
||||
provides its own built-in method to clean up your system, and will provide
|
||||
instructions, but you still may have to do some of the cleaning yourself
|
||||
as discussed above.
|
||||
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-query.html">next</A>; <A href="ch-notinstalled.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,158 @@
|
||||
<html><head>
|
||||
<title>swim - COMMAND LINE OPTION SYNTAX
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 2<br>
|
||||
COMMAND LINE OPTION SYNTAX
|
||||
|
||||
</h1>
|
||||
When you press ``<strong>swim</strong>
|
||||
<<strong>enter</strong>>`` you will see a listing of command line
|
||||
options in a particular syntax. This is to help you understand under what
|
||||
context to use the options. When you enter the options on the command
|
||||
line, the brackets, parentheses, braces, diamonds, and question marks are
|
||||
not actually used.
|
||||
<P>
|
||||
|
||||
|
||||
<strong>Major Mode Option</strong>
|
||||
<P>
|
||||
|
||||
All command line options for <strong>swim</strong> always start with a
|
||||
<strong>major mode option</strong>, except for ``swim <enter>``
|
||||
which will show the whole listing of options. A major mode option is
|
||||
surrounded in braces <strong>{ major mode option }</strong>. In the case
|
||||
of {--search} there are the alternative major mode options
|
||||
{--refinesearch} and {--research}, but because --search needs to be used
|
||||
first before either of these two options, --refinesearch and --research
|
||||
are surrounded in parentheses ().
|
||||
<P>
|
||||
|
||||
Note: Through the other chapters of this manual <strong>{}</strong> is
|
||||
assumed for the <strong>major modes</strong> in the
|
||||
<strong>usage:</strong> section shown at the beginning of every chapter.
|
||||
<P>
|
||||
|
||||
Let's take a closer look at this situation:
|
||||
|
||||
<P>
|
||||
|
||||
<code>{--search ? (--research || --refinesearch)<pattern(s)>}</code>
|
||||
<P>
|
||||
`<strong>||</strong>' or `<strong>|</strong>' are used to indicate
|
||||
`<strong>or</strong>', `<strong>?</strong>' indicates
|
||||
`<strong>optional</strong>', <diamond> indicates an
|
||||
<strong>argument</strong> (a required argument - see Arguments below),
|
||||
(parenthesis) means `if used, must be used after the
|
||||
previous required option was used'. Note: for readability
|
||||
<code>--research</code> and -<code>-refinesearch</code> are not surrounded in
|
||||
<code>{}</code>.
|
||||
<P>
|
||||
|
||||
<strong>Normal Options</strong>
|
||||
<P>
|
||||
|
||||
Options to the major mode options are enclosed in brackets <strong>[
|
||||
option to major mode ]</strong>. <code>swim [-n]</code>
|
||||
<<code>enter</code>> (assume enter from here on out), for instance,
|
||||
will show all the command line options without using the pager. The pager
|
||||
which swim uses can be set in <em>swimrc</em> (see <em>swimrc(8)</em>).
|
||||
``<code>swim {--help} [-n]</code>'' will provide brief explanations of all of
|
||||
swim's options without using the pager. In this case the major mode option
|
||||
<strong>{--help}</strong>, and the option <strong>[-n]</strong> were used.
|
||||
<P>
|
||||
|
||||
<strong>Dashes</strong>
|
||||
<P>
|
||||
|
||||
Options which have a single dash can be combined with other single dashed
|
||||
options <strong>(-qaint)</strong>. Double dashed options need to be
|
||||
entered by themselves <strong>(--help --nopager)</strong>, many double
|
||||
dashed options have an alternative single dash option <strong>(-n for
|
||||
--nopager)</strong>. The meaning of options is related to the major
|
||||
mode they are being used with. <strong>[-n]</strong> means no pager
|
||||
when called with <strong>{--help}</strong>, but it's a reference to the
|
||||
not-installed databases when used with <strong>{-q --query}</strong>,
|
||||
fortunately most options do not have double meanings.
|
||||
<P>
|
||||
|
||||
<strong>Arguments</strong>
|
||||
<P>
|
||||
|
||||
Many options require an argument. Arguments are enclose in diamonds <
|
||||
<strong>argument</strong> >. An argument to an option may also be
|
||||
optional in which case a question mark ``<strong>?</strong>'' will be
|
||||
placed between the option and the argument. <strong>[-l ?
|
||||
<[--df]>]</strong> illustrates such a situation.
|
||||
<strong>[-l]</strong> shows a file listings, and optionally the option
|
||||
<strong>[--df]</strong> can be use with <strong>[-l]</strong> to show an
|
||||
expanded listing.
|
||||
<P>
|
||||
|
||||
<strong>[--dbpath</strong> <<strong>dir>]</strong> requires an
|
||||
argument, this time the argument would not be another option, but rather
|
||||
it is a directory.
|
||||
<P>
|
||||
|
||||
Rule: When an option is an argument to another option it can be written
|
||||
anywhere, but when a non-option is an argument
|
||||
<<strong>dir</strong>> <strong>(notice no brackets)</strong> it has
|
||||
to be placed directly after the option. Sometimes, there may be
|
||||
alternative arguments divided with ``<strong>|</strong>''.
|
||||
<<strong>argument1|argument2</strong>> means use argument1 or
|
||||
argument2, but not both.
|
||||
<P>
|
||||
|
||||
Based on what we now know, let's compare this situation to the
|
||||
<strong>{--search}</strong> situation shown above:
|
||||
<P>
|
||||
|
||||
<code>[--ftp ? --source | --source_only ? <[--diff]>]</code>
|
||||
<P>
|
||||
|
||||
|
||||
In this case <strong>--source</strong> or alternatively
|
||||
<strong>--source_only</strong> can be optionally used along with
|
||||
<strong>--ftp</strong> because they aren't in parentheses
|
||||
<strong>()</strong> (also notice: | was used instead of ||, but means the
|
||||
same thing ``or''). <strong>--diff</strong> can optionally be provided as
|
||||
an argument to either <strong>--source</strong> or
|
||||
<strong>--source_only</strong>. For readability --source and --source_only
|
||||
weren't enclosed in brackets.
|
||||
<P>
|
||||
|
||||
<strong>Global Arguments</strong>
|
||||
<P>
|
||||
|
||||
A <strong>global argument</strong> can be typed anywhere on the command
|
||||
line, and can be an option or text. If global arguments
|
||||
exist they are placed last after the list of normal
|
||||
options that can be used with a major mode
|
||||
option.
|
||||
<P>
|
||||
|
||||
[targets | -S] and [targets|APT|DF] are
|
||||
examples. {-q}, {--initndb}, and
|
||||
{--rebuildndb} all use global arguments.
|
||||
<P>
|
||||
|
||||
<strong>Minor Mode Options</strong>
|
||||
<P>
|
||||
|
||||
{-q --query} will generally use zero or more
|
||||
minor mode options [-afpgn --dir], with
|
||||
one exception (see <A href="ch-query.html">QUERYING THE INSTALLED AND NOT-INSTALLED DATABASES
|
||||
, chapter 9</A>).
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-version.html">next</A>; <A href="ch-description.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,32 @@
|
||||
<html><head>
|
||||
<title>swim - DESCRIPTION
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 1<br>
|
||||
DESCRIPTION
|
||||
|
||||
</h1>
|
||||
|
||||
|
||||
<strong>swim</strong> is a powerful <em>package administration</em>
|
||||
and <em>research tool</em> for both an <em>installed Debian
|
||||
distribution</em>, and/or <em>not-installed virtual Debian
|
||||
distribution(s)</em> allowing querying of software packages with a variety
|
||||
of package information options, and powerful searches. Virtual options
|
||||
which include ftp, installation, and package removal capabilities can be
|
||||
seamlessly combined with querying or searches. <strong>swim</strong> can
|
||||
be used on computer systems which either have, or do not have a Debian
|
||||
distribution installed.
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-commandline.html">next</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,37 @@
|
||||
<html><head>
|
||||
<title>swim - HISTORY
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 4<br>
|
||||
HISTORY
|
||||
|
||||
</h1>
|
||||
|
||||
<pre>
|
||||
usage: swim --history
|
||||
swim -h
|
||||
|
||||
options: [--arch <architecture>] [--dists <distribution>]
|
||||
[--n] [--dbpath <dir>] [--root <dir>]
|
||||
</pre>
|
||||
<P>
|
||||
|
||||
This shows a shell-like history of searches and the most recent --stdin
|
||||
edit. History is numbered with the most recent action being 1, and the
|
||||
earlier actions being of a higher number until the maximum amount of lines
|
||||
set in the HISTORY variable in <code>swimrc(5)</code>. A separate history is
|
||||
kept for each architecture-distribution.
|
||||
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-makinginst.html">next</A>; <A href="ch-version.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,330 @@
|
||||
<html><head>
|
||||
<title>swim - IMPORTANT DEBIAN DATABASES FOR NOT-INSTALLED
|
||||
DATABASES
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 6<br>
|
||||
IMPORTANT DEBIAN DATABASES FOR NOT-INSTALLED
|
||||
DATABASES
|
||||
|
||||
</h1>
|
||||
<hr>
|
||||
<h2><A name="s-downimportant">
|
||||
6.1 A. downloading the important databases with --ftp.
|
||||
|
||||
</A></h2>
|
||||
|
||||
<pre>usage: swim --ftp
|
||||
|
||||
options: --Contents <DF|directory>
|
||||
--Packages <DF|directory>
|
||||
[--dists <distribution>] [--arch <architecture>]
|
||||
[--onec] [--Release_only]</pre>
|
||||
<hr>
|
||||
<h2><A name="s6.2">
|
||||
6.2 OVERVIEW
|
||||
|
||||
</A></h2>
|
||||
<strong>swim</strong> provides a method so that all information about
|
||||
an existing Debian distribution is quickly accessible through databases.
|
||||
Debian already provides flat file databases for all its distributions. One
|
||||
database called ``<em>Contents-(architecture)</em>'' provides a complete
|
||||
listing of all the files associated with each package, the other much more
|
||||
important database called ``<em>Packages</em>'' provides everything from
|
||||
the Package's description, to all the dependencies for that package. The
|
||||
Packages database is a crucial database for other important Debian
|
||||
administrative tools like <strong>dpkg</strong> and <strong>apt</strong>.
|
||||
<hr>
|
||||
<h2><A name="s-dd">
|
||||
6.3 DISTRIBUTION DEFINED
|
||||
|
||||
</A></h2>
|
||||
Debian Distributions choose a name which reflect the development state of
|
||||
that distribution. The distribution named ``<em>unstable</em>'' is where
|
||||
the majority of the development processing occurs, after <em>unstable</em>
|
||||
has reached a certain level of maturity, it's copied over to a new
|
||||
distribution called ``<em>frozen</em>'' which is tested extensively before
|
||||
becoming the new ``<em>stable</em>'' distribution. The <em>frozen
|
||||
distribution</em> retains the <em>Release version number</em> of the
|
||||
<em>unstable distribution</em>, and the <em>unstable distribution</em>
|
||||
receives a new <em>Release version number</em>. Eventually,
|
||||
<em>frozen</em> becomes <em>stable</em>, and at this point both
|
||||
<em>frozen</em>, and the older <em>stable distribution</em> are removed.
|
||||
Code names are associated with the <em>Release Version number</em> given
|
||||
for each of the distributions. This is much better for mirroring Debian
|
||||
sites.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>swim</strong> was designed to ignore these code names, and instead
|
||||
shows the user the <em>Release version number</em> associated with the
|
||||
distribution. Swim users must always use the real distribution name, or
|
||||
swim will not work properly. This is a nice feature because it allows user
|
||||
to make decisions related to the management of their databases, and makes
|
||||
research much more easier.
|
||||
|
||||
<P>
|
||||
|
||||
The other Debian distribution which swim recognizes is
|
||||
<em>experimental</em>. This distribution <em>does not have any Release
|
||||
version number</em>, and contains packages which are considered risky
|
||||
because of their development level.
|
||||
|
||||
|
||||
<P>
|
||||
<hr>
|
||||
<h2><A name="s6.4">
|
||||
6.4 SECTIONS
|
||||
|
||||
</A></h2>
|
||||
Each Debian distribution has sections related to the relationship of
|
||||
each of the packages to the <em>Debian's Policy Manual</em>. In
|
||||
``<em>main</em>'' there are packages which have a correct relationship
|
||||
with these Policies. Packages in ``<em>contrib</em>'' comply with the
|
||||
<em>DFSG</em> (<em>Debian Free Software Guidelines</em> found in the
|
||||
<em>Debian Policy Manual</em>) but have various limitations like requiring
|
||||
a package which is found in non-free, or is not in the Debian archive.
|
||||
Packages in ``<em>non-free</em>'' do not comply with the <em>DFSG</em> but
|
||||
are electronically distributable across international borders. The
|
||||
``<em>non-us</em>'' section is found outside of the United States and
|
||||
exists for packages which have export restrictions.
|
||||
|
||||
|
||||
<P>
|
||||
<hr>
|
||||
<h2><A name="s6.5">
|
||||
6.5 ARCHITECTURES
|
||||
|
||||
</A></h2>
|
||||
Distributions also have architecture specific sections since not all
|
||||
packages compiled for one architecture can run on all other
|
||||
archictectures, however, there are a large percentage of packages which do
|
||||
run on all architectures. The architectures are <em>alpha</em>,
|
||||
<em>arm</em>, <em>i386</em>, <em>m68k</em>, <em>powerpc</em>,
|
||||
<em>sparc</em>, and more recently <em>hurd-i386</em> which represents
|
||||
packages for the hurd GNU kernel for the i386 architecture.
|
||||
|
||||
<P>
|
||||
<hr>
|
||||
<h2><A name="s6.6">
|
||||
6.6 SWIMZ.LIST
|
||||
|
||||
</A></h2>
|
||||
<strong>--ftp</strong> uses a file called <em>swimz.list</em> which
|
||||
has the same type of format (see format below) as the
|
||||
<em>sources.list(5)</em> which <strong>apt</strong> uses. There are some
|
||||
differences. The <strong>first difference</strong> mentioned above (see
|
||||
<A href="#s-dd">DISTRIBUTION DEFINED
|
||||
, section 6.3</A>) requires that the distribution names never should be the
|
||||
code names for the <em>Release version</em>. <strong>Secondly</strong>,
|
||||
<strong>apt</strong> only retrieves databases specific to one
|
||||
archictecture, normally the one you are running <strong>apt</strong> on.
|
||||
With <strong>swim</strong> though you can fetch databases for any, or
|
||||
every architecture by adding the architecture to ``deb'' with a hyphen
|
||||
(deb-hurd-i386). If deb has no architecture appended it is assumed that
|
||||
the architecture you want is the same as the system you are running
|
||||
<strong>swim</strong> on. <strong>Thirdly</strong>, at this time
|
||||
<strong>swim</strong> only supports the ftp method.
|
||||
<strong>Fourthly</strong>, you can change <em>swimz.list</em> as often as
|
||||
you want without worrying about databases being removed so that that the
|
||||
<em>swimz.list</em> and the downloaded databases match. This would occur
|
||||
with <strong>apt's</strong> <em>sources.list(5)</em> if you removed a
|
||||
site. <strong>Fifthly</strong>, databases are kept in a compressed state.
|
||||
<strong>Sixthly</strong> because the list is used for both Contents and
|
||||
Packages, more flexibility is provided by only allowing the default
|
||||
distribution/archictecture or distribution/architecture provided on the
|
||||
commandline to be downloaded.
|
||||
<P>
|
||||
|
||||
|
||||
For <strong>apt</strong> users: If you are using <strong>apt</strong>, and
|
||||
<strong>swim</strong> together it is a good strategy to use the real
|
||||
distribution name in the <em>sources list(8)</em>, and to have an exact
|
||||
copy of the <em>sources.list(5)</em> ftp sites in the <em>swimz.list</em>.
|
||||
Packages databases specific to the architecture <strong>apt</strong> is
|
||||
using can be retrieved using <strong>swim --apt --update</strong> (this
|
||||
also will keep track of the Release version), and then
|
||||
<strong>swim</strong> can be used to fetch the architecture specific
|
||||
<em>Contents database</em> as shown below. It should also be of interest
|
||||
to note that Packages downloaded by either swim or apt can be used
|
||||
interchangeably by using 'cp -a' and 'gzip -d' or 'gzip -9'.
|
||||
<P>
|
||||
|
||||
Here is a brief outline of the format required by <em>swimz.list</em>.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>deb uri distribution [section ... ]</strong>
|
||||
<P>
|
||||
|
||||
<strong>deb</strong> - represents a standard Debian distribution. And is
|
||||
simply written as deb or with the architecture appended
|
||||
(<strong>deb</strong> or <strong>deb-alpha</strong>).
|
||||
|
||||
<P>
|
||||
|
||||
<strong>uri</strong> - Universal Resource Identifier is exactly how you
|
||||
would enter an address into a web browser. This address is the base of a
|
||||
Debian distribution, generally this is right before the directory called
|
||||
``<em>dists</em>''. So if <em>dists</em> is found in
|
||||
<em>/stuff/pub/debian/dists</em>, and the site is
|
||||
<strong>somewhere.com</strong> then the uri would be
|
||||
<em>ftp://somewhere.com/stuff/pub/debian</em>.
|
||||
<P>
|
||||
|
||||
<strong>distribution</strong> - This can be <em>unstable</em>,
|
||||
<em>frozen</em>, <em>stable</em>, <em>experimental</em>. Distribution can
|
||||
also be a path which must end with a slash like
|
||||
<em>unstable/binary-i386/</em>. This is used when there is no section as
|
||||
in the experimental distribution or in sites which do not have symlinks to
|
||||
the non-us section. No section would be mentioned in this situation.
|
||||
<P>
|
||||
<strong>section</strong> - <em>main</em>, <em>contrib</em>,
|
||||
<em>non-free</em>, <em>non-US</em> (write it this way).
|
||||
|
||||
<P>
|
||||
<hr>
|
||||
<h2><A name="s6.7">
|
||||
6.7 SWIMZ.LIST EXAMPLES
|
||||
|
||||
</A></h2>
|
||||
Examples (each on one line):
|
||||
|
||||
<P>
|
||||
|
||||
<strong>deb-alpha ftp://somewhere.com/stuff/pub/debian unstable main contrib non-US</strong>
|
||||
<P>
|
||||
|
||||
This will fetch the alpha databases from somewhere.com for the unstable
|
||||
distribution for the main, contrib and non-US sections.
|
||||
|
||||
<P>
|
||||
|
||||
Note: In these next two examples you can not append any architecture to deb
|
||||
with a hyphen.
|
||||
<P>
|
||||
|
||||
<strong>deb ftp://somewhere.com/stuff/pub/debian project/experimental/</strong>
|
||||
|
||||
<P>
|
||||
|
||||
This will fetch the experimental database, but there is not a
|
||||
Contents-(architecture) database for this distribution. Notice that it ends
|
||||
with a slash.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>deb ftp://somewhere.com/stuff/pub/debian-non-US stable/binary-i386/</strong>
|
||||
<P>
|
||||
|
||||
This will fetch the i386 databases for the stable distribution for non-us,
|
||||
|
||||
<hr>
|
||||
<h2><A name="s-ftp">
|
||||
6.8 FTP OR APT?
|
||||
|
||||
</A></h2>
|
||||
How you use major mode <strong>--ftp</strong> depends on your goals.
|
||||
Even if you are using <strong>apt</strong>, you may be interested in
|
||||
keeping tabs on different architectures. In this case you would have to
|
||||
download the <em>Packages databases</em> specific to these architectures.
|
||||
If you are only interested in the architecture which <strong>apt</strong>
|
||||
is interested in, then you only need to use <strong>--ftp</strong> to
|
||||
fetch the <em>Contents database(s)</em>. But, because it isn't a
|
||||
requirement to set up a virtual filesystem, you are not required to fetch
|
||||
the Contents database. The <strong>advantages</strong> of fetching the
|
||||
Contents database is determined by the method you choose to make the
|
||||
database (see <A href="ch-notinstalled.html">MAKING NOT-INSTALLED DATABASES
|
||||
, chapter 7</A>). These advantages include the
|
||||
ability to <em>view a listing of the files and directories</em> associated
|
||||
with a package, the ability to <em>query files and directories</em> to
|
||||
find out which packages relate to them, and the ability to perform a
|
||||
<em>powersearch</em> on all the files and directories to find the
|
||||
associated packages.
|
||||
<P>
|
||||
<hr>
|
||||
<h2><A name="s6.9">
|
||||
6.9 OPTIONS
|
||||
|
||||
</A></h2>
|
||||
<strong>Remember:</strong> If you want to download a different
|
||||
distribution/architecture other than the default specified in your
|
||||
configuration file, you must specify this on the commandline.
|
||||
<P>
|
||||
<strong>--Packages</strong> determines where you want the Packages
|
||||
database as well as the Release data put when they are downloaded. The
|
||||
<strong>DF argument</strong> implies that the databases will be put in
|
||||
your default directory (see <code>swimrc(5)).</code> These databases can later
|
||||
be located by the major modes <strong>--initndb and --rebuildndb</strong>
|
||||
just by using <strong>DF</strong> as an argument. Alternatively, these
|
||||
databases can be put in any directory you choose by providing a
|
||||
<strong>directory as an argument</strong>.
|
||||
<P>
|
||||
|
||||
<strong>--Contents</strong> determines where you want the
|
||||
<em>Content-(architecture)</em> <code>database(s)</code> put. (see
|
||||
--Packages).
|
||||
<P>
|
||||
|
||||
<strong>--onec</strong> will download only one Contents-arch per
|
||||
distribution/architecture specified on the commandline or by default.
|
||||
<P>
|
||||
|
||||
<strong>--Release_only</strong> will download only the Release data for
|
||||
the <em>swimz.list</em> or particular <em>Package(s)</em> mentioned on the
|
||||
command line.
|
||||
<P>
|
||||
|
||||
<strong>--dists</strong> will only find the distribution which corresponds
|
||||
to the argument provided this option.
|
||||
<P>
|
||||
|
||||
<strong>--arch</strong> will only find the architecture which corresponds
|
||||
to the argument provided this option. The different architecture needs to
|
||||
be specified in swimz.list with a hyphen and the architecture appended to
|
||||
deb (deb-(arch)).
|
||||
<hr>
|
||||
<h2><A name="s6.10">
|
||||
6.10 B. downloading the important databases with apt, and maintenance
|
||||
options.
|
||||
|
||||
</A></h2>
|
||||
usage: <strong>swim --apt</strong>
|
||||
<P>
|
||||
|
||||
options: <strong>[--update] [--clean] [--autoclean] [--check]</strong>
|
||||
|
||||
<P>
|
||||
|
||||
Please read <A href="#s-downimportant">A. downloading the important databases with --ftp.
|
||||
, section 6.1</A> for more information.
|
||||
<P>
|
||||
|
||||
<strong>--update</strong> calls <strong>apt</strong> to download the
|
||||
Packages databases.
|
||||
<P>
|
||||
|
||||
<strong>--clean</strong> is a call to an <strong>apt</strong> option to
|
||||
remove any packages stored in <strong>apt's</strong> storage area for
|
||||
downloaded packages. The default for this storage area is
|
||||
<em>/var/cache/apt/arhives</em>
|
||||
<P>
|
||||
|
||||
<strong>--autoclean</strong> will only clean out packages which are not
|
||||
found in apt's cache.
|
||||
<P>
|
||||
|
||||
<strong>--check</strong> tests and updates apt's cache.
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-notinstalled.html">next</A>; <A href="ch-makinginst.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,180 @@
|
||||
<html><head>
|
||||
<title>swim - MAKING INSTALLED SYSTEM DATABASES
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 5<br>
|
||||
MAKING INSTALLED SYSTEM DATABASES
|
||||
|
||||
</h1>
|
||||
|
||||
<hr>
|
||||
<h2><A name="s-initdb">
|
||||
5.1 Initial database making, and Rebuilding for an
|
||||
Installed system.
|
||||
|
||||
</A></h2>
|
||||
|
||||
<pre>
|
||||
usage: swim --initdb
|
||||
swim --rebuilddb
|
||||
|
||||
options: [--dbpath <dir>] [--root <dir>] [--lowmem]
|
||||
[--split_data <lines>]
|
||||
|
||||
</pre>
|
||||
<P>
|
||||
|
||||
An <em>installed Debian distribution</em> is one in which packages are
|
||||
installed using <strong>dpkg</strong> or some front-end to
|
||||
<strong>dpkg</strong> like <strong>apt</strong> or
|
||||
<strong>dselect</strong>; <strong>swim</strong> supports installation
|
||||
through <strong>apt</strong>. These major modes are for a computer with an
|
||||
<em>installed Debian distribution</em> and make the databases which allow
|
||||
querying and searching capabilities for the installed distribution.
|
||||
<P>
|
||||
|
||||
<strong>--initdb</strong> is run when the databases do not exist yet,
|
||||
<strong>--rebuilddb</strong> is run if the databases have become corrupt,
|
||||
or you want to rebuild the databases instead of updating them.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--dbpath</strong> can be specified as an alternative location for
|
||||
where the databases will be made. The default location is
|
||||
``<em>/var/lib/dpkg</em>''. An argument like ``<em>/otherstuff</em>''
|
||||
could be provided, and then the databases would be made here instead.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--root</strong> allows a database to be made for a Debian distribution installed on a
|
||||
different partition. If the distribution is mounted on
|
||||
<em>/New_Debian</em>, ``<em>/New_Debian</em>'' would be the argument to root. The databases would be made for the
|
||||
Debian distribution installed on the ``<em>/New_Debian</em>'' partition.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--dbpath</strong> and <strong>--root</strong> can be used
|
||||
together. Given the previous two examples, the databases would be made on
|
||||
``<em>/New_Debian/otherstuff</em>'', assuming
|
||||
``<em>/New_Debian/otherstuff</em>'' actually existed.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--lowmem</strong> uses a method which uses a small amount of
|
||||
memory to make the databases. By default <strong>--initdb</strong> and
|
||||
<strong>--rebuilddb</strong> use a method which fully takes advantage of
|
||||
memory, this is a good thing, because it means the databases are made in a
|
||||
quicker manner. On a computer with a K6-200 CPU, 64MB of memory, and 1500
|
||||
installed packages, the databases can be made in 4.5 minutes using the
|
||||
default method, and 11 minutes using the low memory method. The high
|
||||
memory method is the default because in general the size of a distribution
|
||||
is related to how much resources a computer has, and probably a large
|
||||
installation is unusual. If you get an ``out of memory'' when you use the
|
||||
default method, or if your system is overloaded to begin with, the
|
||||
<strong>--lowmem method</strong> is the prefered way.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--split_data</strong> determines the size of the files in the
|
||||
temporary directory used to contruct the database. The default is 25000
|
||||
lines per file. If you are using the <strong>--lowmem method</strong> you
|
||||
may want to provide a different argument to <strong>--split_data</strong>,
|
||||
like ``<strong>--split_data 10000</strong>''. This is a subject of
|
||||
experimentation.
|
||||
<P>
|
||||
<hr>
|
||||
<h2><A name="s5.2">
|
||||
5.2 UPDATING
|
||||
|
||||
</A></h2>
|
||||
usage: <strong>swim --db</strong>
|
||||
|
||||
|
||||
|
||||
<P>
|
||||
|
||||
options: <strong>[--dbpath</strong> <<strong>dir</strong>><strong>]
|
||||
[--root</strong> <<strong>dir</strong>><strong>] [--check]</strong>
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--db</strong> allows you to update the databases by hand when
|
||||
packages have been removed, added, or changed. swim will automatically run
|
||||
<strong>--db</strong> under certain conditions.
|
||||
<P>
|
||||
<strong>--check</strong> prints out the changes to STDERR, and the
|
||||
total to STDOUT without proceeding with the update.
|
||||
<P>
|
||||
|
||||
See <A href="#s-initdb">Initial database making, and Rebuilding for an
|
||||
Installed system.
|
||||
, section 5.1</A> for options <strong>--dbpath</strong> and
|
||||
<strong>--root</strong>.
|
||||
|
||||
<P>
|
||||
<hr>
|
||||
<h2><A name="s-searchy">
|
||||
5.3 REBUILDING THE SEARCH
|
||||
|
||||
|
||||
</A></h2>
|
||||
|
||||
usage: <strong>swim --rebuildflatdb</strong>
|
||||
|
||||
|
||||
|
||||
<P>
|
||||
|
||||
options: <strong>[--dbpath</strong> <<strong>dir</strong>><strong>]
|
||||
[--root</strong> <<strong>dir</strong>><strong>]</strong>
|
||||
|
||||
<P>
|
||||
|
||||
swim makes the flat databases <em>searchindex.deb</em> and
|
||||
<em>dirindex.deb</em> for doing <em>powersearches</em>. Instead of
|
||||
rebuilding these databases everytime <strong>--db</strong> is run, new
|
||||
information is just appended to these databases, and old information is
|
||||
kept. Generally, this is not a problem because only files and directories
|
||||
which the other databases actually know something about will be refered
|
||||
to. But in a situation where a file has changed into a directory, the
|
||||
<em>powersearch</em> may not work properly, because the old file name
|
||||
remains in <em>searchindex.deb</em>, and the new directory name is now in
|
||||
<em>dirindex.deb</em> directory. In general, it takes a lot of changes to
|
||||
the installed system before it is really becomes necessary to rebuild the
|
||||
flat databases. This process takes less than a minute on a K6-200 with
|
||||
1500 packages.
|
||||
|
||||
<P>
|
||||
|
||||
See <A href="#s-initdb">Initial database making, and Rebuilding for an
|
||||
Installed system.
|
||||
, section 5.1</A> for options <strong>--dbpath</strong> and
|
||||
<strong>--root</strong>.
|
||||
<hr>
|
||||
<h2><A name="s5.4">
|
||||
5.4 FILES
|
||||
|
||||
</A></h2>
|
||||
|
||||
Databases which are made:
|
||||
<P>
|
||||
|
||||
<pre> packages.deb
|
||||
fileindex.deb
|
||||
statusindex.deb
|
||||
groupindex.deb
|
||||
searchindex.deb
|
||||
dirindex.deb</pre>
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-important.html">next</A>; <A href="ch-history.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,230 @@
|
||||
<html><head>
|
||||
<title>swim - MAKING NOT-INSTALLED DATABASES
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 7<br>
|
||||
MAKING NOT-INSTALLED DATABASES
|
||||
|
||||
</h1>
|
||||
|
||||
<pre>
|
||||
usage: swim --initndb
|
||||
swim --ndb
|
||||
swim --rebuildndb
|
||||
|
||||
options: [--Contents <target|FDBtarget|DF|FDBDF>]
|
||||
[--main] [--contrib] [--non-free] [--non-us]
|
||||
[--arch <architecture>] [--dists <distribution>]
|
||||
[--dbpath <dir>] [--root <dir>] [--alt]
|
||||
[--split_data <lines>] [-v] [--cron]
|
||||
[targets|APT|DF]
|
||||
</pre>
|
||||
<P>
|
||||
<hr>
|
||||
<h2><A name="s7.1">
|
||||
7.1 OVERVIEW
|
||||
|
||||
</A></h2>
|
||||
The <strong>not-installed database</strong> provides swim with many capabilities like the searching, and querying of
|
||||
packages which do not actually exist on the live filesystem, as well as the
|
||||
ability to seamlessly install packages while searching or quering, or the
|
||||
ability to fetch the packages source code. The <em>virtual filesystem</em> is optional, but it is highly recommended. These two major mode options set
|
||||
up these databases, after determining the level of interaction which you
|
||||
want.
|
||||
<P>
|
||||
|
||||
Whenever <strong>swim</strong> makes databases it thinks only in terms of
|
||||
one distribution and one architecture. This keeps things logical.
|
||||
<strong>swim</strong> does have the ability to take Packages files with
|
||||
multiple architectures, and distributions, and to extract information for
|
||||
one distribution and one archictecture to make its databases. This could
|
||||
provide interesting information from dumps from <strong>apt</strong>
|
||||
(<code>apt-cache dumpavail</code>).
|
||||
<P>
|
||||
|
||||
<strong>--initndb</strong> creates the initial not-installed databases for
|
||||
a particular architecture and distribution, and
|
||||
<strong>--rebuildndb</strong> remakes the not-installed databases for that
|
||||
same architecure and distribution. If not otherwise specified
|
||||
<strong>swim</strong> <em>will use the values</em> it finds in
|
||||
<em>swimrc</em> to determine what architecture and distribution you want
|
||||
to use to make <strong>swim's</strong> databases. Otherwise...
|
||||
|
||||
<hr>
|
||||
<h2><A name="s7.2">
|
||||
7.2 OPTIONS
|
||||
|
||||
</A></h2>
|
||||
<strong>--arch</strong> allows an argument to override the
|
||||
<strong>architecture</strong> found in <em>swimrc</em>.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--dists</strong> allows an argument to override the
|
||||
<strong>distribution</strong> found in <em>swimrc</em>.
|
||||
<P>
|
||||
|
||||
<strong>--alt</strong> is used for a distribution with a Debian archival
|
||||
structure, but which has a different name. This allows for alternative
|
||||
distributions.
|
||||
<P>
|
||||
|
||||
When <strong>APT</strong> or <strong>DF</strong> are provided as arguments
|
||||
(see below), by default the <em>Packages</em> which pertain to the
|
||||
sections found in <em>swimrc</em> will be shown. If you only want certain
|
||||
sections you may specify them on the command line. If you are not using
|
||||
<strong>APT</strong> or <strong>DF</strong>, it is a good idea to make
|
||||
sure that either the sections found in <em>swimrc</em> or the sections you
|
||||
put on the command line match the <em>Packages</em> you a targetting
|
||||
because this is much more effecient.
|
||||
<P>
|
||||
|
||||
<strong>--main</strong> will override the sections found in
|
||||
<em>swimrc</em>, and will use this section.
|
||||
<P>
|
||||
|
||||
<strong>--contrib</strong> will override the sections found in
|
||||
<em>swimrc</em>, and will use this section
|
||||
<P>
|
||||
|
||||
<strong>--non-free</strong> will override the sections found in
|
||||
<em>swimrc</em>, and will use this section
|
||||
<P>
|
||||
|
||||
<strong>--non-us</strong> will override the sections found in
|
||||
<em>swimrc</em>, and will use this section
|
||||
<P>
|
||||
|
||||
Global arguments <strong>targets|APT|DF</strong> must be used with either
|
||||
of these two major modes to find the <em>Packages</em> databases. targets
|
||||
can be a full path to one or a set of <em>Packages</em>.
|
||||
<strong>APT</strong> will use the <em>Packages</em> found in
|
||||
<em>/var/state/apt/lists</em>, and <strong>DF</strong> will use the
|
||||
Packages found in the default directory for <strong>swim</strong> (see
|
||||
<code>--ftp</code>). If you use either <strong>APT</strong> or
|
||||
<strong>DF</strong> you will be given an <strong>interface</strong> which
|
||||
allows you to choose one <em>Packages</em> database for each section you
|
||||
would like to use from the various sites. This <strong>interface</strong>
|
||||
shows the <strong>site</strong>, <strong>date</strong>,
|
||||
<strong>size</strong> and <strong>Release version</strong> for each
|
||||
<em>Packages</em>.
|
||||
<P>
|
||||
|
||||
<strong>--cron</strong> allows you to override the
|
||||
<strong>interface</strong> produced when <strong>APT</strong> or
|
||||
<strong>DF</strong> is provided as an argument. This is useful if you want
|
||||
to automate the database making process. <strong>--cron</strong> will
|
||||
choose the newest <code>database(s),</code> if cron notices that the Release
|
||||
version has changed, cron will not proceed, but will provide a warning
|
||||
instead. This allows you to make the appropriate changes and choices.
|
||||
<P>
|
||||
|
||||
<strong>--Contents</strong> can be give one of four arguments:
|
||||
<P>
|
||||
|
||||
<strong>1).</strong> If you have a <em>Contents-(architecture)</em>
|
||||
database in a target location you know about you may provide a path to the
|
||||
location. The <em>Contents</em> database can be compressed.
|
||||
<P>
|
||||
|
||||
<strong>2).</strong> If you prepend the path with the letters
|
||||
<strong>FDB</strong> (meaning flat database) when the databases for swim
|
||||
are made, instead of using the Contents database to make:
|
||||
|
||||
<pre>
|
||||
nfileindex-arch-dists.deb
|
||||
nsearchindex-arch-dists.deb
|
||||
ndirindex-arch-dists.deb</pre>
|
||||
<P>
|
||||
|
||||
Only the <em>ncontentsindex-arch-dists.deb.gz</em> database will be made
|
||||
which allows the ability to view file/dir listing for not-installed
|
||||
packages, but does not provide the virtual file system or powersearch
|
||||
capabilities which the other databases would have provided.
|
||||
<P>
|
||||
|
||||
<strong>3).</strong> The argument <strong>DF</strong> may be used if you
|
||||
have used <strong>--ftp</strong> with the <strong>DF</strong> argument to
|
||||
the option <strong>--Contents</strong> (see <code>--ftp</code>). In this case
|
||||
it is assumed you are also using global arguments <strong>DF</strong> or
|
||||
<strong>APT</strong> for the Packages databases. This will give you an
|
||||
<strong>interface</strong> (if --cron isn't used) allowing you to choose
|
||||
one <em>Contents</em> database for the particular distribution you want to
|
||||
make the databases for.
|
||||
<P>
|
||||
|
||||
<strong>4).</strong> <strong>FDB</strong> does the same exact thing with
|
||||
<strong>DF</strong> as it does with the before mentioned
|
||||
<strong>FDBtarget</strong>, and provides the <strong>interface</strong>.
|
||||
<P>
|
||||
|
||||
<strong>-v</strong> will only work if you have dpkg installed. It allows
|
||||
swim to verify <strong>swim's</strong> own built-in version comparison
|
||||
function with <strong>dpkg's version comparison function</strong>. This is
|
||||
good for debugging purposes, and produces a report called
|
||||
<em>.version_compare</em> in the same location that
|
||||
<strong>swim's</strong> databases are made.
|
||||
<P>
|
||||
|
||||
<strong>--split_data</strong> is only advantageous if
|
||||
<strong>--Contents</strong> is being used. See <strong>--initdb</strong>
|
||||
for more information about the <strong>--split_data</strong> option.
|
||||
<P>
|
||||
|
||||
See <A href="ch-makinginst.html#s-initdb">Initial database making, and Rebuilding for an
|
||||
Installed system.
|
||||
, section 5.1</A> for options <code>--dbpath</code> and <code>--root</code>.
|
||||
<hr>
|
||||
<h2><A name="s7.3">
|
||||
7.3 UPDATING
|
||||
|
||||
</A></h2>
|
||||
|
||||
<code>--ndb</code> has the same options as --initndb and --rebuildndb except
|
||||
for --split_data. It also has a new option <code>--nue</code> which will
|
||||
never have to be used unless the experimental distribution or non-us
|
||||
section are found in Contents (which presently isn't the case).
|
||||
<code>--check</code> prints out the changes to STDERR, and the total to STDOUT
|
||||
without proceeding with the update. <code>--status_only</code> can be used
|
||||
after a new package has been installed to update the status, after which
|
||||
-qni and -qi will correlate properly.
|
||||
<hr>
|
||||
<h2><A name="s7.4">
|
||||
7.4 REBUILDING THE SEARCH
|
||||
|
||||
</A></h2>
|
||||
<code>--rebuildflatndb</code> serves the same purpose as --rebuildflatdb. See
|
||||
<A href="ch-makinginst.html#s-searchy">REBUILDING THE SEARCH
|
||||
|
||||
, section 5.3</A>
|
||||
<hr>
|
||||
<h2><A name="s7.5">
|
||||
7.5 FILES
|
||||
|
||||
</A></h2>
|
||||
Databases and reports which are made (arch = architecture dists =
|
||||
distribution):
|
||||
<P>
|
||||
|
||||
<pre>
|
||||
npackages-arch-dists.deb
|
||||
nfileindex-arch-dists.deb requires <--Contents>
|
||||
nstatusindex-arch-dists.deb
|
||||
ngroupindex-arch-dists.deb
|
||||
nsearchindex-arch-dists.deb
|
||||
ndirindex-arch-dists.deb
|
||||
.packagesdiff-arch-dists.deb requires <--Contents></pre>
|
||||
<P>
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-aptprep.html">next</A>; <A href="ch-important.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,672 @@
|
||||
<html><head>
|
||||
<title>swim - QUERYING THE INSTALLED AND NOT-INSTALLED DATABASES
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 9<br>
|
||||
QUERYING THE INSTALLED AND NOT-INSTALLED DATABASES
|
||||
|
||||
</h1>
|
||||
<pre>usage: swim -q [-fpgn --dir] [targets | -S]
|
||||
swim --query [-fpgn --dir] [targets | -S]
|
||||
swim -qa || swim --query -a </pre>
|
||||
<P>
|
||||
|
||||
<pre>options: [--total -t] [-i] [-l ? <[--df]>] [-d] [-c]
|
||||
[--scripts] [--preinst] [--postinst] [--prerm]
|
||||
[--postrm] [-v] [--dbpath <dir>] [--menu -m]
|
||||
[--shlibs] [-T] [--pre_depends] [--depends]
|
||||
[--recommends] [--suggests] [--conflicts]
|
||||
[--replaces] [--provides] [--md5sum] [--root <dir>]
|
||||
[--copyright] [--changelog] [--allgroups]
|
||||
[--arch <architecture>] [--dists <distribution>]
|
||||
[--ftp ? --source | --source_only ? <[--diff]>]
|
||||
[--stdin] [--extract] <ALL|archive|PWD!archive>]
|
||||
[-xyrz --remove ? <[--nz]>] [--purge] [--apt2df]
|
||||
[--df2apt] </pre><P>
|
||||
|
||||
global arguments: <strong>[targets | -S ? <\d{1,}>]</strong>
|
||||
<P>
|
||||
|
||||
Quering almost always involves using <strong>-q or --query</strong> with
|
||||
zero or one or a combination of the <strong>minor mode options</strong>
|
||||
(package specification options), and one or more (only one for
|
||||
<code>-g</code>) targets specific to the minor mode, or the results of a
|
||||
search (<code>-S</code>). [<code>-S</code> can be provided a numerical argument
|
||||
pertaining to the past history.] This can be combined with one or more
|
||||
options. The one exception is ``<strong>swim -q --allgroups</strong>''.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--query or -q</strong> can be used by itself or with
|
||||
<strong>-n</strong> to query known package names or package names with
|
||||
versions. ``<strong>swim -q test1 test2_0.3-1</strong>'' would produce the
|
||||
output:
|
||||
|
||||
<P>
|
||||
|
||||
<pre>test1_1.0-2
|
||||
test2_0.3-1</pre>
|
||||
<hr>
|
||||
<h2><A name="s-mm">
|
||||
9.1 MINOR MODES
|
||||
|
||||
</A></h2>
|
||||
<strong>-n</strong> is the minor mode option to access the
|
||||
<em>not-installed system</em>, it can be combined with the minor mode
|
||||
options <strong>-a</strong>, <strong>-g</strong>, <strong>-f</strong>, or
|
||||
it can be used by itself.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>-a</strong> allows <em>every package</em> on an installed or
|
||||
not-installed (<strong>-n</strong>) system to be queried. ``<strong>swim
|
||||
-qan</strong>'' will show all the package names with versions for the
|
||||
not-installed system
|
||||
|
||||
<P>
|
||||
|
||||
<strong>-f</strong> allows <em>files or directories</em> to be queried,
|
||||
when used without any options the package name with version is shown.
|
||||
<strong>--dir</strong> will only query directories, this is useful if you
|
||||
are not sure whether what you are quering is a directory or a file. When a
|
||||
directory is queried, swim shows all packages which exist below the
|
||||
queried directory. ``<strong>swim -qf /</strong>'' is exactly the same as
|
||||
``<strong>swim -qa</strong>''. Hint: ``<strong>swim -qf .</strong>'' and
|
||||
``<strong>swim -qf *</strong>'' are quite different, the first shows all
|
||||
packages which exist below the current directory, and the second will show
|
||||
the package which each file in the current directory comes from.
|
||||
<P>
|
||||
|
||||
<strong>-g</strong> will query a <em>group</em> (also called a section,
|
||||
see <A href="#s-section">SECTION AND PRIORITY
|
||||
, subsection 9.5.3</A>)) of packages. Groups represent subjects which
|
||||
packages with similiar characteristics are catagorized by. To view all the
|
||||
groups found in an installed or not-installed system use ``<strong>swim -q
|
||||
--allgroups</strong>'' or ``<strong>swim -qn --allgroups</strong>''.
|
||||
``<strong>swim -qg hamradio</strong>'' or ``<strong>swim -qng
|
||||
hamradio</strong>'' shows all the package names for the hamradio group.
|
||||
<P>
|
||||
|
||||
<strong>-p</strong> is used to query a <em>Debian package</em>, these
|
||||
packages are distinguished by their ``deb'' ending, but swim can
|
||||
tell whether a file is a debian package even without the ending. Called
|
||||
without any options the package name with version will be shown.
|
||||
<hr>
|
||||
<h2><A name="s-specdata">
|
||||
9.2 SPECIFYING THE DATABASES TO USE
|
||||
|
||||
</A></h2>
|
||||
<strong>--dists</strong> will use the databases for the argument
|
||||
given, otherwise the databases pertaining to the value found in swimrc
|
||||
will be used.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--arch</strong> will use the databases for the argument given,
|
||||
otherwise the databases pertaining to the value found in swimrc will be
|
||||
used.
|
||||
|
||||
<P>
|
||||
|
||||
Example: <strong>swim -qat --arch hurd-i386 --dists unstable</strong>
|
||||
|
||||
<P>
|
||||
|
||||
Assuming these databases exist this will show all packages and their
|
||||
versions for the unstable distribution and architecture hurd-i386 even if
|
||||
the values in <em>swimrc</em> are i386 and stable.
|
||||
|
||||
<P>
|
||||
|
||||
see <A href="ch-important.html#s-downimportant">A. downloading the important databases with --ftp.
|
||||
, section 6.1</A> and <A href="ch-notinstalled.html">MAKING NOT-INSTALLED DATABASES
|
||||
, chapter 7</A> for more
|
||||
information about the databases.
|
||||
|
||||
<hr>
|
||||
<h2><A name="s9.3">
|
||||
9.3 OPTIONS
|
||||
|
||||
</A></h2>
|
||||
<strong>--total or -t</strong> are <em>used to override the output
|
||||
suppressor</em>. The output suppressor will not show output if a certain
|
||||
number of packages is exceeded, instead it will show the number of
|
||||
packages you are querying. This is useful for two reasons, first, knowing
|
||||
the number of packages you are quering can be very informative, second, it
|
||||
gives you a chance to add to the command line a pipe to a pager, ex:
|
||||
``<strong>swim -qat | less</strong>''. You can set the number that the
|
||||
output suppressor works at as high or low as you want in the
|
||||
<em>swimrc(8)</em> file. By design the <strong>-t</strong> option will
|
||||
have to be used if the <strong>-i</strong> option is used and more than
|
||||
one package is being queried. This option can also be used to alter the
|
||||
output of the various script options (--scripts, --preinst, --postinst,
|
||||
--prerm, and --postrm).
|
||||
|
||||
<P>
|
||||
|
||||
<strong>-i</strong> provides <em>information</em> about each package being
|
||||
queried. The format differs slightly for the installed packages versus the
|
||||
not-installed packages. see <A href="#s-format">FORMAT
|
||||
, section 9.5</A>:
|
||||
|
||||
<P>
|
||||
|
||||
<strong>-l</strong> provides a listing of the files associated with a
|
||||
package. If the option <strong>--df</strong> is provided as an argument,
|
||||
all the directories associated with package will be shown. It is important
|
||||
to remember that many packages provide directories which become important
|
||||
to them after they are installed, so the option <strong>--df</strong>
|
||||
often provides necessary information which <strong>-l</strong> called by
|
||||
itself would have not.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>-d</strong> shows the documentation which the package provides
|
||||
found in <em>/usr/doc/*</em>, <em>/usr/man/*</em>, <em>/usr/info/*</em>.
|
||||
Other documentation which the package may provide in a non-standard
|
||||
location will not be shown. <strong>-d</strong> takes precedence over
|
||||
<strong>-l</strong>, so if <strong>-l</strong> is used on the command line
|
||||
with <strong>-d</strong>, only the output for <strong>-d</strong> will be
|
||||
shown.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>-v</strong> is a special option which works only with the minor
|
||||
mode <strong>-p</strong>. It can be used with <strong>-l</strong>,
|
||||
<strong>--df</strong>, <strong>-d</strong>, to show the packages files
|
||||
and/or directories in long format (<code>ls -
|
||||
l</code>).
|
||||
|
||||
<P>
|
||||
|
||||
<strong>-c</strong> will show the configuration files packages use. If the
|
||||
package does not have a configuration file then nothing will be shown. The
|
||||
output will show the file and its path indented one space with the
|
||||
<strong>MD5 checksum</strong>. This will not work with
|
||||
<strong>-n</strong>.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--scripts</strong> shows all scripts associated with a package
|
||||
with the name of the script presented before each script in this way
|
||||
<strong>#####scriptname######</strong>. If the scripts are called
|
||||
individually by using the script options <strong>--preinst</strong>,
|
||||
<strong>--postinst</strong>, <strong>--prerm</strong>, or
|
||||
<strong>--postrm</strong> no title is shown, this is nice for writing to a
|
||||
file. If <strong>-t</strong> is used with the individual script options a
|
||||
title will be shown, this makes sense because normally only individual
|
||||
packages would be queried to write a script to a file, and
|
||||
<strong>-t</strong> wouldn't be used in this situation. Scripts are the
|
||||
soul of Debianized packages allowing packages to be installed, configured,
|
||||
and removed seamlessly and cleanly under all kinds of conditions. These
|
||||
options do no work with <strong>-n</strong>.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--menu or -m</strong> is used to view menufiles which belong to
|
||||
various packages. If the package does not have a menufile nothing will be
|
||||
shown. This option can be useful in troubleshooting a menu entry which
|
||||
does not seem to work, or in finding out where the menu entry is.
|
||||
<em>Joost Witteveen's Debian menu system</em> is a centralized program
|
||||
which interacts with all kinds of menus. <em>Please read the
|
||||
documentation</em> ``<strong>swim -qd menu</strong>'' which comes with the
|
||||
menu package to find out more. This will not work with
|
||||
<strong>-n</strong>.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--shlibs</strong> shows a list of shared libraries certain
|
||||
packages supply. The <em>Debian Packaging Manual</em> (packaging-manual)
|
||||
provides detailed information about the format of a shlibs file. This will
|
||||
not work with <strong>-n</strong>.
|
||||
<P>
|
||||
|
||||
<strong>--md5sum</strong> checks <strong>MD5 checksums</strong>. It can be
|
||||
used with <strong>-l</strong>, <strong>-d</strong>, <strong>-c</strong>,
|
||||
or <strong>-p</strong>. If there are checksums available the md5sum result
|
||||
will be either <strong>OK</strong>, <strong>FAILED</strong>, or
|
||||
<strong>MISSING</strong>. <strong>MISSING</strong> means that although a
|
||||
checksum exists, the file can not be found. The result is put after the
|
||||
file and its path and the <strong>MD5 checksum</strong> or the package
|
||||
name and version and the <strong>MD5 checksum</strong>.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--copyright</strong> does a case insensitive search for copy or
|
||||
license in the <em>/usr/doc/packagename</em> directory. This should show
|
||||
how the package relates to <em>Debian's Policy Manual</em>.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--changelog</strong> searches for any files in
|
||||
<em>/usr/doc/packagename</em> which look like changelogs. Debian packages
|
||||
always have a <em>Maintainer's</em> changelog for the package. There may
|
||||
be a separate changelog kept by the author of the program.
|
||||
<hr>
|
||||
<h2><A name="s9.4">
|
||||
9.4 PACKAGE RELATIONSHIPS
|
||||
|
||||
</A></h2>
|
||||
|
||||
<strong>-T</strong> shows all the package relationships of packages.
|
||||
Individual package relationships can be viewed using
|
||||
<strong>--pre_depends</strong>, <strong>--depends</strong>,
|
||||
<strong>--recommends</strong>, <strong>--suggests</strong>,
|
||||
<strong>--replaces</strong>, <strong>--conflicts</strong> or
|
||||
<strong>--provides</strong>. Package relationships are the spirit of
|
||||
Debian packages, here is a quick overview briefly reiterating what can be
|
||||
found in the <em>Debian Packaging Manual</em>. <em>Package
|
||||
Maintainers</em> set these relationships in control file fields of the
|
||||
same name.
|
||||
<P>
|
||||
|
||||
<strong>Dependencies</strong>
|
||||
|
||||
<em>Pre-depends</em> - means that the pre-depended package or packages
|
||||
must be installed before the queried package can be installed. Most
|
||||
packages which have pre-dependencies are usually essential and required
|
||||
packages.
|
||||
|
||||
<P>
|
||||
|
||||
<em>Depends</em> - declares an absolute dependency to another package or
|
||||
packages either <em>real or virtual</em>. The queried package cannot
|
||||
function without this other package.
|
||||
|
||||
<P>
|
||||
|
||||
<em>Recommends</em> - declares a strong, but not absolute dependency to
|
||||
another package or packages either <em>real or virtual</em>. You would
|
||||
usually find the recommended package together with the queried package in
|
||||
a normal installation.
|
||||
|
||||
<P>
|
||||
|
||||
<em>Suggests</em> - can be one or more packages either <em>real or
|
||||
virtual</em> which would be useful to the queried package, but are not
|
||||
necessary.
|
||||
|
||||
|
||||
<strong>Alternative Packages</strong>
|
||||
<P>
|
||||
|
||||
<em>Conflicts</em> - is a package or packages either <em>real or
|
||||
virtual</em> which would cause problems with the queried package, and
|
||||
would not be allowed to be installed while the queried package was
|
||||
installed.
|
||||
<P>
|
||||
|
||||
<strong>Overwriting files and Replacing Packages</strong>
|
||||
<P>
|
||||
|
||||
<em>Replaces</em> - allows the queried package to replace another package
|
||||
or packages by overwriting their files, after which the previous package
|
||||
would be considered to have disappeared. Essentially this allows the
|
||||
queried package to take over the package or packages. In a situation where
|
||||
there was a Conflict between the queried package and these packages this
|
||||
field would help determine which packages should be removed.
|
||||
<P>
|
||||
|
||||
<strong>Virtual Packages</strong>
|
||||
<P>
|
||||
|
||||
<em>Provides</em> - declares a virtual package which may be mentioned in
|
||||
<em>Depends</em>, <em>Recommends</em>, <em>Suggests</em>, or
|
||||
<em>Conflicts</em>. <em>Virtual packages</em> allow one or more packages
|
||||
to share the same name of another package, which means if the queried
|
||||
package has a reference to a virtual package in one of the before
|
||||
mentioned package relationship fields, then whatever packages provide the
|
||||
virtual package are also being listed.
|
||||
<hr>
|
||||
<h2><A name="s-format">
|
||||
9.5 FORMAT
|
||||
|
||||
</A></h2>
|
||||
|
||||
<strong>1). Installed system</strong>
|
||||
|
||||
<P>
|
||||
|
||||
<pre> Package: name Status: hold ok installed
|
||||
Version: 1.1-1 Essential: no
|
||||
Section: namers Priority: extra
|
||||
Installed-Size: 10 Source: generatename (2.0-1)
|
||||
Maintainer: name <name@name.org>
|
||||
Description: hostname maker
|
||||
A nice way to figure out a hostname nobody
|
||||
else has.</pre>
|
||||
<P>
|
||||
|
||||
<strong>2) Not-installed system</strong>
|
||||
|
||||
|
||||
|
||||
<P>
|
||||
|
||||
<pre> Package: name Status: r> hold ok installed (1.1-1)
|
||||
Version: 1.1-2 Essential: no
|
||||
Section: names Priority: extra
|
||||
Installed-Size: 11 Source: generatename (2.0-1)
|
||||
Size: 43000 Architecture: i386
|
||||
Distribution: experimental
|
||||
Maintainer: name <name@name.org>
|
||||
Description: hostname maker
|
||||
A nice way to figure out a hostname nobody
|
||||
else has.</pre>
|
||||
<P>
|
||||
|
||||
There are several things to point out. The difference between the two
|
||||
outputs relates to the addition of the Distribution, Size, and
|
||||
Architecture fields for the not-installed query. Installed-Size is how
|
||||
many kilobytes the package will occupy when it is unpacked, whereas Size
|
||||
is the size in bytes of the package.
|
||||
<hr>
|
||||
<h3><A name="s9.5.1">
|
||||
9.5.1 STATUS FIELD
|
||||
|
||||
</A></h3>
|
||||
|
||||
|
||||
The Status field provides the installation status of the package, this
|
||||
holds true for the not-installed query as well. In a sense, the
|
||||
not-installed database isn't always not-installed. If the not-installed
|
||||
package is actually already installed, and the version numbers are exactly
|
||||
the same, then the status will be the same for either query. If the
|
||||
not-installed package is not installed then the status will be
|
||||
``not-installed''. In cases where the not-installed package is already
|
||||
installed, swim uses it's comparison function to figure out whether it is
|
||||
a newer of older package which is installed. In the above example, swim
|
||||
realizes the same package is installed, and only the debian-revision has
|
||||
changed, hence the only difference is that the revision number is greater
|
||||
``r>'' for the not-installed package. When only the debian-revision has
|
||||
changed it can safely be assumed that the author (creator, programmer) of
|
||||
the same program has not made any changes to the same program, but the
|
||||
Debian maintainer has made a change to an aspect of the package like a
|
||||
change in the script the package uses to properly install. You may have
|
||||
also noticed that the status field shows the version number of the
|
||||
installed package enclosed in parenthesis.
|
||||
<hr>
|
||||
<h3><A name="s9.5.2">
|
||||
9.5.2 SOURCE FIELD
|
||||
|
||||
</A></h3>
|
||||
|
||||
The Source field is present in these examples, but the Source field will
|
||||
not always be present for packages. In cases where the name of the source
|
||||
package is the same as the the name found in the Package field, and the
|
||||
version number of the source package is also the same as found in the
|
||||
Version field, then there will be no Source field. In the above examples
|
||||
there is a Source field. In this case name was probably one of many
|
||||
packages generated from the source package called generatename. In this
|
||||
particular example generatename also has its own unique version number
|
||||
2.0-1 enclosed in parentheses, if no version number had been mentioned
|
||||
then the source package would have the same version number as found in the
|
||||
Version field.
|
||||
<hr>
|
||||
<h3><A name="s-section">
|
||||
9.5.3 SECTION AND PRIORITY
|
||||
|
||||
</A></h3>
|
||||
|
||||
Section shows the subject which a package is categorized with (see
|
||||
<code>-g</code>). Priority shows how important the package is to have
|
||||
installed. In the case of the not-installed databases the information for
|
||||
these fields is almost always available from the Packages databases, but
|
||||
this is not always the case for Debian packages. For packages which do no
|
||||
provide this information swim will do its best to fill in the blanks from
|
||||
information found in the installed and not-installed databases. If proper
|
||||
information can not be found it will be indicated as ``unavailable'' or
|
||||
``unknown.'' Unavailable would indicate that information about the package
|
||||
exists, but it is from a different version (includes debian-revision), and
|
||||
no information exists for this version. Unknown means no similiar package
|
||||
exists, and there is absolutely no information about this package in the
|
||||
databases.
|
||||
<P>
|
||||
|
||||
When a Debian package is queried using the <strong>-p</strong>
|
||||
option you will get output like the first example shows, the status field
|
||||
is also calculated.
|
||||
<hr>
|
||||
<h2><A name="s-vrftp">
|
||||
9.6 FTP - VIRTUAL OPTIONS
|
||||
|
||||
</A></h2>
|
||||
|
||||
For ftp capabilities swim uses the <em>swimz.list</em> to determine which
|
||||
sites it will check for the requested packages. The first site which fills
|
||||
the request will be used, otherwise <strong>swim</strong> will go through
|
||||
all the sites avoiding repeats, and if no sites can fill the request,
|
||||
<strong>swim</strong> will either quit or proceed on to check for another
|
||||
request.
|
||||
<P>
|
||||
|
||||
<strong>--ftp</strong> allows the queried package, its source package, or
|
||||
just the source package diff to be downloaded while being queried. This is
|
||||
refered to as virtual downloading because the quering and the downloading
|
||||
are seamless as though the package already exists locally. This has to be
|
||||
used with the option <strong>-n</strong> because packages which which are
|
||||
not part of the not-installed database are considered to already have been
|
||||
downloaded. Packages which are already installed can be downloaded or
|
||||
their source retrieved by setting up a database which corresponds to these
|
||||
packages; if the installed packages belong to the stable distribution,
|
||||
set-up the not-installed stable databases.
|
||||
<P>
|
||||
|
||||
Packages or source code are placed in an area below the default directory
|
||||
mirroring the remote directory they were downloaded from after their size
|
||||
and modification times are checked for correct values. This area is called
|
||||
the <strong>DF</strong> directory, and although this directory mirrors
|
||||
remote directories, it is not an exact mirror, but specific to the
|
||||
requirements of swim because code names for Release versions are not taken
|
||||
into account. For real mirroring capabilities there exist many excellent
|
||||
programs. If a package has a <strong>MD5 checksum</strong>,
|
||||
<strong>--md5sum</strong> will automatically be run and the value shown.
|
||||
Regardless of whether or not the md5sum check is <strong>OK</strong> or
|
||||
not, the package will still be put in the <strong>DF</strong> directory to
|
||||
allow the package to be looked at, so watch the output from
|
||||
<strong>--ftp</strong> to check for <strong>FAILED md5sums</strong>.
|
||||
|
||||
<P>
|
||||
|
||||
Packages or source code packages will not be downloaded again if they are
|
||||
found in the <strong>DF</strong> directory unless their
|
||||
<em>upstream-version</em> has changed in the not-installed database, if
|
||||
the packages are not in the DF directory and the remote
|
||||
<em>upstream-version</em> is different than the not-installed
|
||||
<em>upstream-version</em> then the packages will not be downloaded until
|
||||
the not-installed database is updated or rebuilt to reflect the version
|
||||
change. Changes in the package's <em>upstream-version</em> indicates that
|
||||
the <code>author(s)</code> of the program have made changes to the computer
|
||||
code for the program contained in the package or the source code package.
|
||||
On the other hand, swim will check for a <em>debian-revision</em> change
|
||||
at the remote site if the package can not immediately be found. If the
|
||||
package's <em>debian-revision</em> has changed and the package does not
|
||||
exist locally in the <strong>DF</strong> directory, it will be downloaded.
|
||||
This is a nice feature, especially for the unstable distribution, because
|
||||
it tends to extend the time needed before the not-installed database has
|
||||
to be updated or rebuilt to match the changes at remote sites.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--source</strong> is used with <strong>--ftp</strong> to download
|
||||
the source code package. <strong>--source_only</strong> will download the
|
||||
source code package without the deb package. <em>Source packages consist
|
||||
of three files</em>. The <em>source control file</em> which ends in
|
||||
``dsc'', the <em>original source archive</em> which is a compressed tar
|
||||
file, and the <em>unified context diff</em> showing the changes necessary
|
||||
to make the original source into Debian source. The diff can be downloaded
|
||||
by itself if <strong>--diff</strong> is provided as an argument to
|
||||
<strong>--source or --source_only</strong>.
|
||||
|
||||
<P>
|
||||
|
||||
For <strong>apt</strong> users: <strong>apt</strong> allows packages to be
|
||||
downloaded, but if more than one package is required for the package
|
||||
relationships to be proper, <strong>apt</strong> will download all these
|
||||
packages. <strong>--ftp</strong> allows specific packages to be
|
||||
downloaded, packages from other architectures, and source packages to be
|
||||
downloaded, here lies the advantage of this option over using <strong>-xyz
|
||||
--nz</strong> (see below). If a particular package has been dowloaded into
|
||||
the <strong>DF</strong> directory and it is needed by <strong>apt</strong>
|
||||
for installation, simply copy or move the package from the
|
||||
<strong>DF</strong> directory to <em>/var/cache/apt/archives</em> before
|
||||
running <strong>apt</strong>, and the package will not be downloaded by
|
||||
<strong>apt</strong> again; future versions of <strong>swim</strong> will
|
||||
have an option to automatically accomplish this (see <code>--df2apt</code>).
|
||||
<hr>
|
||||
<h2><A name="s-vrapt">
|
||||
9.7 APT - VIRTUAL OPTIONS
|
||||
|
||||
</A></h2>
|
||||
|
||||
apt-get(8) is a nice package relationship checker from the
|
||||
<strong>apt</strong> package which figures out what needs to be done to
|
||||
properly install a package or packages when one or more package names are
|
||||
provided to it. <strong>apt-get</strong> will get all packages which are
|
||||
needed using a variety of methods, and then <strong>apt-get</strong>
|
||||
interacts with <strong>dpkg</strong> in a way which allows for a
|
||||
successful installation.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>-xyrz, --remove, and --nz</strong> can be used if
|
||||
<strong>apt-get</strong> from the <strong>apt</strong> package is
|
||||
installed. These options allow for what is refered to as virtual
|
||||
installation/removal. It is prudent to always test what will happen by
|
||||
using the <strong>-x</strong> option alone before actually proceeding with
|
||||
the installation with the <strong>-z</strong> option. <strong>-x</strong>
|
||||
will actually simulate what would happen in an installation, showing which
|
||||
and how many packages will be changed, which and how many new packages
|
||||
will need to be installed, which and how many packages will need to be
|
||||
removed, any conflicts, and what needs to be configured.
|
||||
<strong>-y</strong> will automatically answer yes to any prompts
|
||||
<strong>apt-get</strong> may produce allowing <strong>apt-get</strong> to
|
||||
run non-interactively. <strong>-z</strong> as mentioned before actually
|
||||
proceeds with the installation using <strong>dpkg</strong> after the
|
||||
<strong>apt-get</strong> gets the packages. You can append a minus sign
|
||||
to a package name to cause it to be removed. <strong>--nz</strong> when
|
||||
used as an optional argument with <strong>-xz or -xyz</strong> will only
|
||||
download the packages into <em>/var/cache/apt/archives</em> or into
|
||||
whatever directory you configured for holding archives for
|
||||
<strong>apt</strong>.
|
||||
<P>
|
||||
|
||||
<strong>IMPORTANT</strong>: <strong>apt</strong> makes it so easy to make
|
||||
changes to your installation that it is highly recommended to do your
|
||||
research with swim first. This can be done by checking package
|
||||
relationships, file/dir listings, comparing the not-installed package to
|
||||
an installed package if such exists, checking <strong>--md5sum</strong>
|
||||
and <strong>-c</strong> for the installed package, and checking the Source
|
||||
field by running a <strong>--search</strong> (see <A href="ch-search.html">SEARCHING
|
||||
, chapter 11</A>) to
|
||||
check to see how the source package has been split into binary packages
|
||||
for the not-installed package versus an installed package if such exists.
|
||||
Ofcourse, there are many other things you could look at, and you can
|
||||
always do your research after the fact. Presently <strong>--db</strong> is
|
||||
run only by hand, so you can check the old state after an installation if
|
||||
you have not already run <strong>--db</strong>, yourself.
|
||||
<hr>
|
||||
<h2><A name="s-vrrm">
|
||||
9.8 REMOVING AN INSTALLED PACKAGE - VIRTUAL OPTIONS
|
||||
|
||||
</A></h2>
|
||||
|
||||
<strong>--purge</strong> uses <strong>dpkg</strong> to remove an installed
|
||||
package or packages and the configuration files as shown with
|
||||
``<strong>swim -qc packagename</strong>''.
|
||||
<P>
|
||||
|
||||
<strong>-r or --remove</strong> removes an installed package or packages
|
||||
with <strong>apt</strong>, but not the configuration files as shown with
|
||||
``<strong>swim -qc packagename</strong>''. You may also append a plus
|
||||
sign to a package name to cause it to be installed. This option is used
|
||||
with -x or -x(y)z.
|
||||
<hr>
|
||||
<h2><A name="s9.9">
|
||||
9.9 STDIN - VIRTUAL OPTIONS
|
||||
|
||||
</A></h2>
|
||||
|
||||
<strong>--stdin</strong> works with either <strong>--ftp</strong>,
|
||||
<strong>-x</strong>, <strong>-xyz</strong>, <strong>-xz</strong>,
|
||||
<strong>--purge</strong>, <strong>-r</strong>, or
|
||||
<strong>--remove</strong>.
|
||||
<P>
|
||||
|
||||
<strong>--stdin</strong> provides the <em>readline capabilities</em>
|
||||
commonly found in shells allowing you to edit what is on the command line.
|
||||
You can edit the command line, press enter and then recall the history,
|
||||
and make more changes, or <em>type in exit to process the changed or
|
||||
unchanged command line</em>. To find out more about what readline commands
|
||||
your shell supports please read the man pages which apply to your shell.
|
||||
Information for the bash shell can be found in <code>bash(1)</code> under the
|
||||
title ``<strong>Readline Command Names</strong>''.
|
||||
<P>
|
||||
|
||||
Example: ``<strong>swim -qgnx --stdin hamradio</strong>'' will list all
|
||||
the packages from the not-installed hamradio group on the command line,
|
||||
this list can be edited then submitted to <strong>apt-get</strong> for a
|
||||
simulated installation. Another instance of <strong>swim</strong> can be
|
||||
run at the same time, perhaps ``<strong>swim -qinTg hamradio</strong>'' to
|
||||
help in making editing decisions for <strong>--stdin</strong>.
|
||||
<hr>
|
||||
<h2><A name="s9.10">
|
||||
9.10 PACKAGE MANIPULATION - VIRTUAL OPTIONS
|
||||
|
||||
</A></h2>
|
||||
|
||||
<strong>--extract</strong> only works with the <strong>minor mode
|
||||
-p</strong> to extract parts or all of a Debian package. If the
|
||||
<strong>argument ALL</strong> is provided then <em>everything found in the
|
||||
package will be extracted</em> below the current directory in the exact
|
||||
directories found in the package. A particular <em>file may be extracted
|
||||
in its exact location</em> below the current directory by <em>entering the
|
||||
exact path for the file</em> as shown by ``<strong>swim -qpl</strong>'' or
|
||||
``<strong>swim -qpd</strong>'' as the argument. Alternativily, a <em>file
|
||||
may be extracted in the current directory</em> regardless of its proper
|
||||
location by <em>prepending PWD\! before the path</em> shown by
|
||||
``<strong>swim -qpl</strong>'' or ``<strong>swim -qpd</strong>''. Notice
|
||||
the backslash before the exclamation point, this is because shells
|
||||
consider ! a special character, so it has to be backslashed so that the
|
||||
shell knows that it is not such a special character. Example:
|
||||
``<strong>swim -qpi --extract PWD\!usr/bin/name --scripts
|
||||
name_1.1-2.deb</strong>'' will extract the binary name in the current
|
||||
directory from the name package, show information for the name package,
|
||||
and show any scripts for the name package.
|
||||
<hr>
|
||||
<h2><A name="s-dblocus">
|
||||
9.11 DATABASE LOCATIONS
|
||||
|
||||
</A></h2>
|
||||
|
||||
<strong>--dbpath</strong> can be specified as an alternative location for
|
||||
where the databases would be found. The default location is
|
||||
``<em>/var/lib/dpkg</em>''. An argument like ``<em>/otherstuff</em>'' can
|
||||
be provided, and then the databases would be found here instead.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--root</strong> allows a database to be found for a Debian
|
||||
distribution installed on a different partition. If the distribution is
|
||||
mounted on <em>/New_Debian</em>, ``<em>/New_Debian</em>'' would be the
|
||||
argument to root. The databases would be found for the Debian distribution
|
||||
installed on the ``<em>/New_Debian</em>'' partition.
|
||||
<P>
|
||||
|
||||
<strong>--dbpath and --root</strong> can be used together. Given the
|
||||
previous two examples, the databases would be found on
|
||||
``<em>/New_Debian/otherstuff</em>'', assuming
|
||||
``<em>/New_Debian/otherstuff</em>'' actually existed.
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch10.html">next</A>; <A href="ch-aptprep.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,82 @@
|
||||
<html><head>
|
||||
<title>swim - RAMDISK
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 12<br>
|
||||
RAMDISK
|
||||
|
||||
</h1>
|
||||
|
||||
<pre>usage: swim --ramdiskon
|
||||
swim --ramdiskoff
|
||||
|
||||
options: [-n] [--searchfile] [--arch <architecture>]
|
||||
[--dists <distribution>] [--dbpath] [--root]
|
||||
|
||||
no options for --ramdiskoff
|
||||
</pre>
|
||||
<P>
|
||||
<hr>
|
||||
<h2><A name="s12.1">
|
||||
12.1 OVERVIEW
|
||||
|
||||
</A></h2>
|
||||
|
||||
A ramdisk can be mounted below the default path or the specified path for
|
||||
the databases in the dramdisk directory. The ramdisk is used to speed up
|
||||
powersearchs and/or file/dir listings for packages from the not-installed
|
||||
system. Also, this is useful if a computer system is heavily loaded with
|
||||
other processes using the memory, and the ramdisk tends to persist even
|
||||
after being unmounted. Modern kernels usually are built with support for
|
||||
ramdisks. If these options do not work the kernel will need to be compiled
|
||||
to support ramdisks by answering yes to RAM disk support. Perhaps the best
|
||||
<em>README</em> showing how to configure and compile a kernel comes with
|
||||
the <em>kernel sources</em> in the main directory.
|
||||
<P>
|
||||
|
||||
<strong>--ramdiskon</strong> allows a ramdisk to be created and mounted.
|
||||
If called with <strong>-n</strong> (not-installed databases)
|
||||
<em>ncontents-arch-dists.deb.gz</em> will automatically be written to the
|
||||
mounted ramdisk. This provides faster file/dir listing capabilities when
|
||||
using <strong>-l</strong>, <strong>--df</strong>, or <strong>-d</strong>
|
||||
when querying the not-installed system. Faster powersearch capabilities
|
||||
are available through the option <strong>--searchfile</strong>. If the
|
||||
search databases are not already compressed, they will now be compressed,
|
||||
this usually only needs to be done once or until the databases are updated
|
||||
or rebuilt again. The search databases will then be written to the mounted
|
||||
ramdisk. An installed system only writes the search databases to the
|
||||
mounted ramdisk, so always use --searchfile when specifying installed
|
||||
system databases.
|
||||
<P>
|
||||
|
||||
<strong>--ramdiskoff</strong> is used to unmount the ramdisk. The
|
||||
not-installed databases and the installed databases can not be
|
||||
simultaneously provided by a mounted ramdisk, use
|
||||
<strong>--ramdiskoff</strong> first, then <strong>--ramdiskon</strong> to
|
||||
install the other databases of choice. This also pertains to different
|
||||
distributions and/or architectures.
|
||||
<P>
|
||||
|
||||
|
||||
See the section ``<A href="ch-query.html#s-specdata">SPECIFYING THE DATABASES TO USE
|
||||
, section 9.2</A>'' for
|
||||
options <strong>--arch</strong>, <strong>-dists</strong>.
|
||||
<P>
|
||||
|
||||
See the section ``<A href="ch-query.html#s-dblocus">DATABASE LOCATIONS
|
||||
, section 9.11</A>'' for options
|
||||
<strong>--dbpath</strong> and <strong>--root</strong>.
|
||||
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch13.html">next</A>; <A href="ch-search.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,191 @@
|
||||
<html><head>
|
||||
<title>swim - SEARCHING
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 11<br>
|
||||
SEARCHING
|
||||
|
||||
</h1>
|
||||
|
||||
<pre>usage: swim --search ? (--research || --refinesearch) <pattern(s)>
|
||||
swim --powersearch ? (--research || --refinesearch) <pattern(s)>
|
||||
swim --ps ? (--research || --refinesearch) <pattern(s)>
|
||||
|
||||
options: [-g] [-n] [--dbpath <dir>] [--root <dir>] [--no]
|
||||
[--arch <architecture>] [--dists <distribution>
|
||||
[--ftp ? --source | --source_only <[--diff]>]
|
||||
[-xyrz --remove ? <[--nz]>] [--stdin] [--apt2df]
|
||||
[--no] [--df2apt] [--purge] [<\d{1,}>]
|
||||
|
||||
[--dir] and no [-g]for --powersearch or --ps
|
||||
</pre>
|
||||
|
||||
<P>
|
||||
<hr>
|
||||
<h2><A name="s11.1">
|
||||
11.1 OVERVIEW
|
||||
|
||||
</A></h2>
|
||||
|
||||
|
||||
<strong>swim</strong> provides two major types of searches. A search with
|
||||
<strong>--search</strong> <em>searches package information</em> (see <A href="ch-query.html#s-format">FORMAT
|
||||
, section 9.5</A>), and a search with <strong>--powersearch or --ps</strong>
|
||||
<em>searches package information, and all files and/or directories
|
||||
associated with each package</em>.
|
||||
<P>
|
||||
|
||||
The results of either of these searches can be <em>narrowed down</em> by
|
||||
running a test search with <strong>--research</strong> (this step can be
|
||||
skipped) and/or setting the results in stone with
|
||||
<strong>--refinesearch</strong>. <strong>--search</strong> can be
|
||||
<em>narrowed down</em> initially by specifying a particular
|
||||
<em>group</em>, and <strong>--powersearch</strong> can be
|
||||
<em>expanded</em> initially by specifying that <em>directories</em> be
|
||||
searched as well as files. Both searches can <em>use the same virtual
|
||||
options</em> which the major mode <strong>-q or --query</strong> use.
|
||||
Generally, it is preferable to run a search, and then to provide the
|
||||
results of a search (<strong>using -S</strong>) as an argument to
|
||||
<strong>-q or --query</strong>; this allows the results of a search to be
|
||||
queried. Every time a search is run the results are appended to the
|
||||
history, past searches can be refined or researched by providing the
|
||||
numerical argument pertaining to the history. \d{1,} is simply Perl
|
||||
notation meaning a number with one of more digits.
|
||||
|
||||
<P>
|
||||
|
||||
<em>Perl regexps</em> (see <code>perlre(1p))</code> can be used to define the
|
||||
pattern (string) provided as an argument to a search. Do not surround a
|
||||
pattern in slashes, a slash is only used after all patterns and before the
|
||||
<em>modifiers i and/or m</em> (swim supports these two modifiers). To
|
||||
search for more than one pattern, patterns are separated with <em>bars
|
||||
(|)</em>. Patterns may include <em>quatifiers, and metacharacters</em>,
|
||||
also found in <code>egrep(1).</code>
|
||||
<P>
|
||||
|
||||
If a search finds any packages which match the search, the package
|
||||
information will be displayed as the package is found. The package will
|
||||
only be shown once regardless of how many times it is found while the
|
||||
search progresses. When the search is over the number of packages found is
|
||||
shown.
|
||||
<P>
|
||||
|
||||
<strong>--search</strong> provides a search of package information. This
|
||||
is similiar to grepping ``<strong>swim -qait</strong>'' or ``<strong>swim
|
||||
-qaint</strong>'', but it is significantly faster. A search can be
|
||||
performed on a particular group by using <strong>-g</strong> with a group
|
||||
as an argument
|
||||
<P>
|
||||
|
||||
<strong>--powersearch</strong> is somewhat similiar to ``<strong>dpkg
|
||||
--search</strong>'' which searches all files and directories on an
|
||||
installed system, but it combines <strong>--search</strong> with the file
|
||||
and/or directory search, and can also be performed on a not-installed
|
||||
system. A <em>powersearch</em> is significantly faster than the search
|
||||
which <strong>dpkg</strong> provides (even more so when ``<code>swim
|
||||
--ramdiskon --searchfile</code>'' is used) and even more importantly
|
||||
provides a logical output of the search (like ``<code>swim -qi
|
||||
packagename</code>''). By default a search of all directories is not
|
||||
performed because usually this is redundant except in rare cases. To
|
||||
enable a search of all directories use the <strong>--dir</strong> option.
|
||||
<hr>
|
||||
<h2><A name="s11.2">
|
||||
11.2 NARROWING A PREVIOUS SEARCH
|
||||
|
||||
</A></h2>
|
||||
|
||||
<strong>--research</strong> allows the results of a previous search to be
|
||||
researched without making the new results permanent.
|
||||
<P>
|
||||
|
||||
<strong>--refinesearch</strong> allows the results of a previous search to
|
||||
be researched while making the
|
||||
new results permanent.
|
||||
<P>
|
||||
|
||||
<strong>\d{1,}</strong> is a numerical argument to refine or research a
|
||||
past search from the history.
|
||||
<hr>
|
||||
<h2><A name="s11.3">
|
||||
11.3 MINOR MODES
|
||||
|
||||
</A></h2>
|
||||
|
||||
<strong>-n</strong> allows the not-installed databases to be searched.
|
||||
These databases will not exist if the not-installed databases were made
|
||||
with the FDB argument (see <code>--initndb</code>).
|
||||
<P>
|
||||
|
||||
<strong>-g</strong> (see -g above and <A href="ch-query.html#s-mm">MINOR MODES
|
||||
, section 9.1</A>).
|
||||
<hr>
|
||||
<h2><A name="s11.4">
|
||||
11.4 OTHER OPTIONS
|
||||
|
||||
</A></h2>
|
||||
|
||||
<strong>--no</strong> prevents normal output from a search, but does show
|
||||
how many packages were found.
|
||||
<P>
|
||||
|
||||
See the section ``<A href="ch-query.html#s-specdata">SPECIFYING THE DATABASES TO USE
|
||||
, section 9.2</A>'' for options
|
||||
<strong>--arch</strong>, <strong>-dists</strong>.
|
||||
<P>
|
||||
|
||||
See the section ``<A href="ch-query.html#s-vrftp">FTP - VIRTUAL OPTIONS
|
||||
, section 9.6</A>'' for
|
||||
<strong>--ftp</strong>, <strong>--source</strong>,
|
||||
<strong>--source_only</strong>, <strong>--diff</strong>,
|
||||
<P>
|
||||
|
||||
See the section ``<A href="ch-query.html#s-vrapt">APT - VIRTUAL OPTIONS
|
||||
, section 9.7</A>'' for
|
||||
<strong>-xyz</strong>, <strong>--nz</strong>, <strong>--stdin</strong>,
|
||||
<P>
|
||||
|
||||
See the section ``<A href="ch-query.html#s-vrrm">REMOVING AN INSTALLED PACKAGE - VIRTUAL OPTIONS
|
||||
, section 9.8</A>'' for
|
||||
<strong>--purge</strong>, <strong>--remove</strong>, <strong>-r</strong>.
|
||||
|
||||
<P>
|
||||
|
||||
See the section ``<A href="ch-query.html#s-dblocus">DATABASE LOCATIONS
|
||||
, section 9.11</A>'' for options
|
||||
<strong>--dbpath</strong> and <strong>--root</strong>.
|
||||
|
||||
<hr>
|
||||
<h2><A name="s11.5">
|
||||
11.5 EXAMPLES
|
||||
|
||||
</A></h2>
|
||||
|
||||
<strong>swim -gn hamradio --search "radio network/i" --dbpath
|
||||
/test --arch alpha</strong>
|
||||
<P>
|
||||
|
||||
will search the alpha architecture not-installed system databases in the
|
||||
/test directory for all package information from the hamradio group using
|
||||
the case insensitive pattern ``radio network''.
|
||||
<P>
|
||||
|
||||
<strong>swim --powersearch dpkg -xn</strong>
|
||||
<P>
|
||||
|
||||
will search the not-installed system databases for all package information
|
||||
and all files using the case sensitive pattern dpkg, after which apt-get
|
||||
will run a simulation of what would happen if it got and installed these
|
||||
packages.
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-ramdisk.html">next</A>; <A href="ch10.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,23 @@
|
||||
<html><head>
|
||||
<title>swim - SEE ALSO
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 14<br>
|
||||
SEE ALSO
|
||||
|
||||
</h1>
|
||||
|
||||
<code>swimrc(5),</code> apt-get(8), sources.list(5), <code>dpkg(8)</code>
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch15.html">next</A>; <A href="ch13.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,26 @@
|
||||
<html><head>
|
||||
<title>swim - VERSION
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 3<br>
|
||||
VERSION
|
||||
|
||||
</h1>
|
||||
usage: <strong>swim --version</strong>
|
||||
<P>
|
||||
|
||||
This shows the version for the swim program.
|
||||
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-history.html">next</A>; <A href="ch-commandline.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,64 @@
|
||||
<html><head>
|
||||
<title>swim - UPGRADING WITH APT
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 10<br>
|
||||
UPGRADING WITH APT
|
||||
|
||||
</h1>
|
||||
|
||||
usage: <strong>swim --apt</strong>
|
||||
<P>
|
||||
|
||||
options: <strong>[-xyz] [--upgrade] [--dist_upgrade]</strong>
|
||||
<P>
|
||||
|
||||
<strong>apt-get</strong> provides powerful methods to change an
|
||||
installion. When these methods are called using <strong>--apt</strong>,
|
||||
<strong>swim</strong> will not allow you to proceed until you are
|
||||
absolutely sure this is what you want to do. Before using these methods do
|
||||
a ``<strong>swim --apt --update</strong>'' so that
|
||||
<strong>apt-get</strong> knows the newest versions of available packages.
|
||||
This major mode requires a combination of <strong>-x</strong>,
|
||||
<strong>-xz</strong> or <strong>-xyz</strong> to be used along with either
|
||||
<strong>--upgrade</strong> or <strong>--dist_upgrade</strong>.
|
||||
<strong>-x</strong> used alone will simulate what would happen if
|
||||
<strong>-xz or -xyz</strong> were used (also see <code>-xyz</code> above).
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--upgrade</strong> is somewhat similiar to doing ``<strong>swim
|
||||
-qatxz</strong>'' except that it is a more intelligent method because
|
||||
<strong>apt</strong> does some behind the scene calculations in regards to
|
||||
package relationships, in fact the ``<strong>swim -qatxz</strong>''
|
||||
approach will provide totally different results, or maybe these were the
|
||||
results you really wanted. ``<strong>swim --apt --upgrade -xz</strong>''
|
||||
is the prefered, proper, and built-in way provided by
|
||||
<strong>apt-get</strong> to install the newest versions for all packages
|
||||
installed on your system. This method will not install any newer versions
|
||||
of packages which would change the install status of other packages. Note:
|
||||
It is not recommended to combine the query option <strong>-a</strong> with
|
||||
<strong>-xz or -xyz</strong>, but combining the query option
|
||||
<strong>-a</strong> just with <strong>-x</strong> can be educational.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--dist_upgrade</strong> combines an <strong>--upgrade</strong>
|
||||
with the installation of packages which are not installed. This method
|
||||
carefully examines dependencies, and resolves conflicts, and given these
|
||||
factors it will upgrade the most important packages before considering the
|
||||
installation of less important packages. Less important packages will be
|
||||
installed only if there are not any conflicts.
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-search.html">next</A>; <A href="ch-query.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,29 @@
|
||||
<html><head>
|
||||
<title>swim - FILES
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 12<br>
|
||||
FILES
|
||||
|
||||
</h1>
|
||||
|
||||
Configuration files:
|
||||
<P>
|
||||
|
||||
<pre>
|
||||
swimz.list
|
||||
swimrc
|
||||
</pre>
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-seealso.html">next</A>; <A href="ch-ramdisk.html">back</A>.
|
||||
<br>
|
||||
<address>12 March 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,29 @@
|
||||
<html><head>
|
||||
<title>swim - FILES
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 13<br>
|
||||
FILES
|
||||
|
||||
</h1>
|
||||
|
||||
Configuration files:
|
||||
<P>
|
||||
|
||||
<pre>
|
||||
swimz.list
|
||||
swimrc
|
||||
</pre>
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-seealso.html">next</A>; <A href="ch-ramdisk.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,20 @@
|
||||
<html><head>
|
||||
<title>swim - BUGS</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 15<br>
|
||||
BUGS
|
||||
</h1>
|
||||
Send directly to mttrader@access.mountain.net.
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-seealso.html">back</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,64 @@
|
||||
<html><head>
|
||||
<title>swim - UPGRADING WITH APT
|
||||
</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>
|
||||
swim - chapter 9<br>
|
||||
UPGRADING WITH APT
|
||||
|
||||
</h1>
|
||||
|
||||
usage: <strong>swim --apt</strong>
|
||||
<P>
|
||||
|
||||
options: <strong>[-xyz] [--upgrade] [--dist_upgrade]</strong>
|
||||
<P>
|
||||
|
||||
<strong>apt-get</strong> provides powerful methods to change an
|
||||
installion. When these methods are called using <strong>--apt</strong>,
|
||||
<strong>swim</strong> will not allow you to proceed until you are
|
||||
absolutely sure this is what you want to do. Before using these methods do
|
||||
a ``<strong>swim --apt --update</strong>'' so that
|
||||
<strong>apt-get</strong> knows the newest versions of available packages.
|
||||
This major mode requires a combination of <strong>-x</strong>,
|
||||
<strong>-xz</strong> or <strong>-xyz</strong> to be used along with either
|
||||
<strong>--upgrade</strong> or <strong>--dist_upgrade</strong>.
|
||||
<strong>-x</strong> used alone will simulate what would happen if
|
||||
<strong>-xz or -xyz</strong> were used (also see <code>-xyz</code> above).
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--upgrade</strong> is somewhat similiar to doing ``<strong>swim
|
||||
-qatxz</strong>'' except that it is a more intelligent method because
|
||||
<strong>apt</strong> does some behind the scene calculations in regards to
|
||||
package relationships, in fact the ``<strong>swim -qatxz</strong>''
|
||||
approach will provide totally different results, or maybe these were the
|
||||
results you really wanted. ``<strong>swim --apt --upgrade -xz</strong>''
|
||||
is the prefered, proper, and built-in way provided by
|
||||
<strong>apt-get</strong> to install the newest versions for all packages
|
||||
installed on your system. This method will not install any newer versions
|
||||
of packages which would change the install status of other packages. Note:
|
||||
It is not recommended to combine the query option <strong>-a</strong> with
|
||||
<strong>-xz or -xyz</strong>, but combining the query option
|
||||
<strong>-a</strong> just with <strong>-x</strong> can be educational.
|
||||
|
||||
<P>
|
||||
|
||||
<strong>--dist_upgrade</strong> combines an <strong>--upgrade</strong>
|
||||
with the installation of packages which are not installed. This method
|
||||
carefully examines dependencies, and resolves conflicts, and given these
|
||||
factors it will upgrade the most important packages before considering the
|
||||
installation of less important packages. Less important packages will be
|
||||
installed only if there are not any conflicts.
|
||||
<hr>
|
||||
swim
|
||||
- <A href="index.html#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="index.html#toc">Contents</A>; <A href="ch-search.html">next</A>; <A href="ch-query.html">back</A>.
|
||||
<br>
|
||||
<address>12 March 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
@@ -0,0 +1,162 @@
|
||||
<html><head>
|
||||
<title>swim</title>
|
||||
<link rev=made href="mailto:mttrader@access.mountain.net">
|
||||
</head><body>
|
||||
<h1>swim</h1>
|
||||
|
||||
<h2><A name="toc">
|
||||
0.1 Table of contents
|
||||
</A></h2>
|
||||
<ul>
|
||||
<li><A href="ch-description.html">1 DESCRIPTION
|
||||
</A>
|
||||
<li><A href="ch-commandline.html">2 COMMAND LINE OPTION SYNTAX
|
||||
</A>
|
||||
<li><A href="ch-version.html">3 VERSION
|
||||
</A>
|
||||
<li><A href="ch-history.html">4 HISTORY
|
||||
</A>
|
||||
<li><A href="ch-makinginst.html">5 MAKING INSTALLED SYSTEM DATABASES
|
||||
</A>
|
||||
<ul>
|
||||
<li><A href="ch-makinginst.html#s-initdb">5.1</A> Initial database making, and Rebuilding for an
|
||||
Installed system.
|
||||
|
||||
<li><A href="ch-makinginst.html#s5.2">5.2</A> UPDATING
|
||||
|
||||
<li><A href="ch-makinginst.html#s-searchy">5.3</A> REBUILDING THE SEARCH
|
||||
|
||||
|
||||
<li><A href="ch-makinginst.html#s5.4">5.4</A> FILES
|
||||
|
||||
</ul>
|
||||
<li><A href="ch-important.html">6 IMPORTANT DEBIAN DATABASES FOR NOT-INSTALLED
|
||||
DATABASES
|
||||
</A>
|
||||
<ul>
|
||||
<li><A href="ch-important.html#s-downimportant">6.1</A> A. downloading the important databases with --ftp.
|
||||
|
||||
<li><A href="ch-important.html#s6.2">6.2</A> OVERVIEW
|
||||
|
||||
<li><A href="ch-important.html#s-dd">6.3</A> DISTRIBUTION DEFINED
|
||||
|
||||
<li><A href="ch-important.html#s6.4">6.4</A> SECTIONS
|
||||
|
||||
<li><A href="ch-important.html#s6.5">6.5</A> ARCHITECTURES
|
||||
|
||||
<li><A href="ch-important.html#s6.6">6.6</A> SWIMZ.LIST
|
||||
|
||||
<li><A href="ch-important.html#s6.7">6.7</A> SWIMZ.LIST EXAMPLES
|
||||
|
||||
<li><A href="ch-important.html#s-ftp">6.8</A> FTP OR APT?
|
||||
|
||||
<li><A href="ch-important.html#s6.9">6.9</A> OPTIONS
|
||||
|
||||
<li><A href="ch-important.html#s6.10">6.10</A> B. downloading the important databases with apt, and maintenance
|
||||
options.
|
||||
|
||||
</ul>
|
||||
<li><A href="ch-notinstalled.html">7 MAKING NOT-INSTALLED DATABASES
|
||||
</A>
|
||||
<ul>
|
||||
<li><A href="ch-notinstalled.html#s7.1">7.1</A> OVERVIEW
|
||||
|
||||
<li><A href="ch-notinstalled.html#s7.2">7.2</A> OPTIONS
|
||||
|
||||
<li><A href="ch-notinstalled.html#s7.3">7.3</A> UPDATING
|
||||
|
||||
<li><A href="ch-notinstalled.html#s7.4">7.4</A> REBUILDING THE SEARCH
|
||||
|
||||
<li><A href="ch-notinstalled.html#s7.5">7.5</A> FILES
|
||||
|
||||
</ul>
|
||||
<li><A href="ch-aptprep.html">8 PREPARING YOUR INSTALLATION FOR APT
|
||||
</A>
|
||||
<li><A href="ch-query.html">9 QUERYING THE INSTALLED AND NOT-INSTALLED DATABASES
|
||||
</A>
|
||||
<ul>
|
||||
<li><A href="ch-query.html#s-mm">9.1</A> MINOR MODES
|
||||
|
||||
<li><A href="ch-query.html#s-specdata">9.2</A> SPECIFYING THE DATABASES TO USE
|
||||
|
||||
<li><A href="ch-query.html#s9.3">9.3</A> OPTIONS
|
||||
|
||||
<li><A href="ch-query.html#s9.4">9.4</A> PACKAGE RELATIONSHIPS
|
||||
|
||||
<li><A href="ch-query.html#s-format">9.5</A> FORMAT
|
||||
|
||||
<li><A href="ch-query.html#s-vrftp">9.6</A> FTP - VIRTUAL OPTIONS
|
||||
|
||||
<li><A href="ch-query.html#s-vrapt">9.7</A> APT - VIRTUAL OPTIONS
|
||||
|
||||
<li><A href="ch-query.html#s-vrrm">9.8</A> REMOVING AN INSTALLED PACKAGE - VIRTUAL OPTIONS
|
||||
|
||||
<li><A href="ch-query.html#s9.9">9.9</A> STDIN - VIRTUAL OPTIONS
|
||||
|
||||
<li><A href="ch-query.html#s9.10">9.10</A> PACKAGE MANIPULATION - VIRTUAL OPTIONS
|
||||
|
||||
<li><A href="ch-query.html#s-dblocus">9.11</A> DATABASE LOCATIONS
|
||||
|
||||
</ul>
|
||||
<li><A href="ch10.html">10 UPGRADING WITH APT
|
||||
</A>
|
||||
<li><A href="ch-search.html">11 SEARCHING
|
||||
</A>
|
||||
<ul>
|
||||
<li><A href="ch-search.html#s11.1">11.1</A> OVERVIEW
|
||||
|
||||
<li><A href="ch-search.html#s11.2">11.2</A> NARROWING A PREVIOUS SEARCH
|
||||
|
||||
<li><A href="ch-search.html#s11.3">11.3</A> MINOR MODES
|
||||
|
||||
<li><A href="ch-search.html#s11.4">11.4</A> OTHER OPTIONS
|
||||
|
||||
<li><A href="ch-search.html#s11.5">11.5</A> EXAMPLES
|
||||
|
||||
</ul>
|
||||
<li><A href="ch-ramdisk.html">12 RAMDISK
|
||||
</A>
|
||||
<ul>
|
||||
<li><A href="ch-ramdisk.html#s12.1">12.1</A> OVERVIEW
|
||||
|
||||
</ul>
|
||||
<li><A href="ch13.html">13 FILES
|
||||
</A>
|
||||
<li><A href="ch-seealso.html">14 SEE ALSO
|
||||
</A>
|
||||
<li><A href="ch15.html">15 BUGS</A>
|
||||
</ul>
|
||||
<hr><h2><A name="copyright">0.2 Copyright</A></h2>
|
||||
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
<P>
|
||||
|
||||
SWIM, including this manual, is free software; you
|
||||
may 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, or (at your option) any later
|
||||
version.
|
||||
<P>
|
||||
|
||||
This is distributed in the hope that it will be useful, but
|
||||
<em>without any warranty</em>; without even the implied
|
||||
warranty of merchantability or fitness for a particular
|
||||
purpose. See the GNU General Public License for more
|
||||
details.
|
||||
<P>
|
||||
|
||||
You should have received a copy of the GNU General Public
|
||||
License with the <kbd>swim</kbd> source as the file
|
||||
<code>COPYING</code>. If not, write to the Free Software
|
||||
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
|
||||
<hr>
|
||||
swim
|
||||
- <A href="#copyright">
|
||||
Copyright © 1999 Jonathan D. Rosenbaum
|
||||
</A>
|
||||
<br>
|
||||
<A href="#toc">Contents</A>.
|
||||
<br>
|
||||
<address>15 June 1999<br>
|
||||
Jonathan D. Rosenbaum<A href="mailto:mttrader@access.mountain.net">mttrader@access.mountain.net</A></address>
|
||||
</body></html>
|
||||
Reference in New Issue
Block a user