This tool can be opened using .
A service pack is a tarball which contains a set of packages and their dependencies.
To explain better what a service pack is, it is best to show a few use-cases.
You can add multiple packages to a service pack by separating the package
names with a comma, for instance hal,gnome-power-manager.
-
You have seven desktops you've just installed with Fedora 9.
Each one needs to have 204Mb of updates installed.
-
You have a laptop that needs network drivers before it can download updates,
and you have a similar up to date laptop with internet access nearby.
The network drivers require a few dependencies, and other packages to be
upgraded before they will install.
-
You frequently install Linux on other peoples computers.
You carry around a live-cd and a pendrive with a single 204Mb file
Fedora-updates-SP1.servicepack which contains all the
updates since last week.
-
A free software magazine wants to distribute patent encumbered multimedia
plugins and programs with the latest Fedora release DVD.
They want a way in which even the most lazy user can get the things
installed without much fuss.
Internally, the pack file is just an uncompressed tarball, with the packages
and a single metadata.conf file inside.
The metadata file is just the distribution identifier and the time of creation.
This ensures you don't try installing a fedora-9-i386
service pack on a ubuntu-intrepid-ppc machine.
We need a destination file list because we not know what packages are
installed on the destination computer.
For example:
Computer A has the following packages installed, and has internet access.
- glib
- dbus
- dbus-glib
- libgnome
Computer B has the following packages installed, and does not have internet access.
- glib
- dbus
- kdebase
- kdeapps
Computer B wants to have a service pack containing a new version of
k3b so that it can burn DVD-RWs.
The k3b program has dependancies of dbus,
dbus-glib and kdebase.
Now, if we asked computer A to download k3b, it would download
k3b and kdebase but
not dbus-glib.
We need to provide computer A with the information about what packages computer B
has got installed before we can create the service pack.
If we generate a package list on computer B, and the transfer it to
computer A on a USB pendrive or CDRW we can download the correct packages.
In this case we would download k3b and
dbus-glib and pack it into the new service pack.
The service pack can now be transferred from computer A to computer B on
the USB pendrive.
The pkgenpack command line tool can also be used for
creating service pack files.
关于
版权
- 版权 © 2008 Richard Hughes (richard@hughsie.com)
版权通告
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
License (GFDL), Version 1.1 or any later version published
by the Free Software Foundation with no Invariant Sections,
no Front-Cover Texts, and no Back-Cover Texts. You can find
a copy of the GFDL at this link or in the file COPYING-DOCS
distributed with this manual.
This manual is part of a collection of GNOME manuals
distributed under the GFDL. If you want to distribute this
manual separately from the collection, you can do so by
adding a copy of the license to the manual, as described in
section 6 of the license.
Many of the names used by companies to distinguish their
products and services are claimed as trademarks. Where those
names appear in any GNOME documentation, and the members of
the GNOME Documentation Project are made aware of those
trademarks, then the names are in capital letters or initial
capital letters.
DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED
UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE
WITH THE FURTHER UNDERSTANDING THAT:
-
DOCUMENT IS PROVIDED ON AN "AS IS" BASIS,
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES
THAT THE DOCUMENT OR MODIFIED VERSION OF THE
DOCUMENT IS FREE OF DEFECTS MERCHANTABLE, FIT FOR
A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE
RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE
OF THE DOCUMENT OR MODIFIED VERSION OF THE
DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR
MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT,
YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY
CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY
SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER
OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS
LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED
VERSION OF THE DOCUMENT IS AUTHORIZED HEREUNDER
EXCEPT UNDER THIS DISCLAIMER; AND
-
UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL
THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE),
CONTRACT, OR OTHERWISE, SHALL THE AUTHOR,
INITIAL WRITER, ANY CONTRIBUTOR, OR ANY
DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION
OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH
PARTIES, BE LIABLE TO ANY PERSON FOR ANY
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES OF ANY CHARACTER
INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS
OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR
MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR
LOSSES ARISING OUT OF OR RELATING TO USE OF THE
DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT,
EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF
THE POSSIBILITY OF SUCH DAMAGES.
Feedback
To report a bug or make a suggestion regarding the gnome-packagekit application or
this manual, follow the directions in the
gnome-packagekit Contact Page.