Browse files

update install and readme

  • Loading branch information...
1 parent 9b81716 commit 645071f8d308f4be6d838bc7361d35a4f956fcee Seth Vidal committed Aug 31, 2004
Showing with 5 additions and 27 deletions.
  1. +4 −5 INSTALL
  2. +1 −22 README
@@ -1,8 +1,7 @@
For usage information, please see the README.
-yum uses a relatively standard ./configure ; make ; make install to
-work, although it is recommended that you install an RPM as yum
-requires that it be installed as an RPM.
+run make
+run make install, if you're a masochist.
+you're better off making an rpm and installing it
-If checking code out of CVS, you will need to run autoconf first to
-create the configure script.
@@ -3,8 +3,7 @@ Yum - an automatic updater and installer for rpm-based systems
Included programs:
-/usr/sbin/yum Main program
-/usr/sbin/yum-arch Generate the database that yum downloads
+/usr/bin/yum Main program
Basic usage description follows:
@@ -25,23 +24,3 @@ Yum is run with one of the following options:
- yum list [package list]
List available packages
-yum-arch is run from the distribution site in order to create the
-databases which Yum determines remote package availability.
-yum-arch is run in one of two ways:
- yum-arch <top level of archive>
-Theory of operation/use:Yum works by providing the headers of all the rpm packages in any system
-repository. These headers are stored on the webserver in a subdir of the
-top level of the repository. The client downloads all of the headers of
-the packages it doesn't have installed or of packages that have been updated.
-It uses the headers to determine the dependencies it will need using rpm's internal
-dependency calculation. Once it knows what rpms it will need it downloads them and
-performs the transaction.
-Multiple repositories - explanation of how it came out/why.
-Explanation of why not apt-rpm

0 comments on commit 645071f

Please sign in to comment.