--- arch-install-guide.txt 2009-02-07 00:07:01.000000000 +0530 +++ arch-install-guide.txt 2009-02-07 00:36:04.000000000 +0530 @@ -342,7 +342,7 @@ been properly installed, and that it is supported by the Linux kernel. When the correct module is loaded, and your desired network card is - listed, you should Select the ethernet device you want to configure + listed, you should select the ethernet device you want to configure and you will be given the option to configure your network with DHCP. If your network uses DHCP, hit YES and let the installer do the rest. If you select NO, you will be asked to enter the networking information @@ -1385,24 +1385,24 @@ Typical tasks: - 1. Adding a new package with a package file - 2. Upgrading a package with a package file - 3. Removing packages - 4. Refreshing the package list - 5. Upgrading the system - 6. Adding/Upgrading a package from the repositories - 7. List installed packages - 8. Check if a specific package is installed - 9. Display specific package info - 10. Display list of files contained in package - 11. Find out which package a specific file belongs to + 1. Adding or upgrading a new package with a package file + 2. Removing packages + 3. Refreshing the package list + 4. Upgrading the system + 5. Adding/Upgrading a package from the repositories + 6. List installed packages + 7. Check if a specific package is installed + 8. Display specific package info + 9. Display list of files contained in package + 10. Find out which package a specific file belongs to - Adding a new package with a package file + Adding or upgrading a new package with a package file - # pacman --add foo.pkg.tar.gz - # pacman -A foo.pkg.tar.gz + # pacman --upgrade foo.pkg.tar.gz + # pacman -U foo.pkg.tar.gz - This will install the foo.pkg.tar.gz package on the system. If + If package foo is not currently installed on the system, then + this will install the foo.pkg.tar.gz package on the system. If dependencies are missing, pacman will exit with an error and report the missing deps, but not attempt to resolve the dependencies automatically. Look at the --sync option if you expect this @@ -1410,16 +1410,9 @@ listed files depend on each other, the packages will be automatically installed in the correct order. - Upgrading a package with a package file - - # pacman --upgrade foo.pkg.tar.gz - # pacman -U foo.pkg.tar.gz - - This does essentially the same as the --add operation, but will - additionally upgrade an already-installed package at no extra cost. I - can personally not imagine a case where you'd prefer --add over this - --upgrade function, unless you want pacman to exit if a package is - already installed. + If package foo is already installed, then this operation will replace + the version installed on the system with the package specified on the + command line. Removing packages @@ -1474,9 +1467,8 @@ Retrieve and install package foo, complete with all dependencies it requires. Before using any sync option, make sure you refreshed the package list, or add --refresh or -y to the options to do it before - the installation attempt. Unlike --add, the --sync option does not - differ between installing and upgrading packages. Depending on your - pacman.conf settings this function requires working Internet access. + the installation attempt. Depending on your pacman.conf settings + this function requires working Internet access. Receiving strange errors when downloading packages from the server, ie. broken downloads or files that aren't found, usually are either @@ -1575,26 +1567,12 @@ Synchronizing Your ABS Tree You can synchronize all the required package building files in - /var/abs by running the abs script as root. It requires the cvsup - package to operate and will complain if you don't have it installed. A - working Internet connection is also required, of course. Using CVS as - the transfer medium allows you to follow different version trees - within ABS - this can be configured in /etc/abs/supfile.core. For - example, the default supfile is set to track the current package tree, - which is bleeding-edge and the recommended source to follow. You can - also follow specific versions. See the comments in the supfiles for - more info. + /var/abs by running the abs script as root. A working internet + connection is required, of course. ABS supports multiple repositories, which can be enabled or disabled - in /etc/abs/abs.conf. By default, abs will follow the core and - extra repositories, but not anything else. - - You will also see an /etc/abs/supfile.extra file. This will give you - access to all the unofficial build scripts that were not included in - the main ABS repository. If you do not want to use this repository, - you can delete the file, but usually it makes more sense to edit - abs.conf accordingly instead, and disable the repositories you don't - need. + in /etc/abs.conf. By default, abs will follow core, extra, community + and the testing repositories. How to Build Packages @@ -1645,7 +1623,7 @@ /usr/lib Libraries /usr/include Header files /usr/lib/{pkg} Modules, plugins, etc. - /usr/man Manpages + /usr/share/man Manpages /usr/share/{pkg} Application data /etc/{pkg} Configuration files for {pkg} /opt @@ -1671,14 +1649,12 @@ 3. Unpacks source files 4. Does any necessary patching 5. Builds the software and installs it in a fake root - 6. Removes /usr/doc, /usr/info, /usr/share/doc, and /usr/share/info - from the package - 7. Strips symbols from binaries - 8. Strips debugging symbols from libraries - 9. Generates the package meta file which is included with each + 6. Strips symbols from binaries + 7. Strips debugging symbols from libraries + 8. Generates the package meta file which is included with each package - 10. Compresses the fake root into the package file - 11. Stores the package file in the configured destination directory + 9. Compresses the fake root into the package file + 10. Stores the package file in the configured destination directory (cwd by default) Other