Update documentation to match with reality.

--HG--
extra : convert_revision : xtraeme%40gmail.com-20090821060205-m1zc41d0b0zqtsf5

doc/BINPKG_REPOSITORY

@@ -83,6 +83,10 @@ setting in the configuration file:
 
 	$ xbps-repo genindex /path/to/dir
 
+Alternatively if you only want to register a single package:
+
+	$ xbps-repo add-pkgidx /package/repo /package/repo/<arch>/foo-1.2.xbps
+
 After this you can add your own local repository with binary packages:
 
 	$ xbps-repo add /path/to/dir
@@ -108,9 +112,9 @@ To show information about available packages in the repository pool:
 
 	$ xbps-repo show package
 
-To search for binary packages by specifying a string:
+To search for binary packages by specifying a shell pattern (see fnmatch(3)):
 
-	$ xbps-repo search mypkg
+	$ xbps-repo search 'foo*'
 
 ------------------------------------------------------------------------------
 	Juan Romero Pardines <xtraeme@gmail.com>

doc/README

@@ -2,19 +2,16 @@
  WHAT IS IT?
 -----------------------------------------------------------------------------
 
-xbps - xtraeme's build package system.
+xbps - xtraeme's binary package ystem.
 
-It is a simple build package system that installs packages inside of
+xbps is a new binary package system, taken ideas from other free available
-a chroot in a destination directory. Once the package has been installed
+implementations, such as dpkg/apt, RPM, pacman and others. Metadata handling
-into this directory, you can make it appear/unappear at the master directory
+as package databases are handled by proplib. Multiple compression formats
-at any time. It's in spirit the same than GNU stow, but the files are just
+are supported in binary packages thanks to libarchive.
-copied (there are no soft/hard links).
 
 xbps has been designed for Linux, and for the moment I'm not interested to
-make it work on any other random OS. I've been a NetBSD developer for some
+make it work on any other random OS. xbps is the base to create a basic
-years and I do not want to come back... also the experience has helped to
+Linux system.
-me to start xbps and not to use pkgsrc, which is very portable but also
-not so fast.
 
 -----------------------------------------------------------------------------
  REQUIREMENTS
@@ -29,11 +26,12 @@ http://code.google.com/p/portableproplib/
 I'm also the human maintaining the portable proplib package. I'd suggest you
 to install it into /usr/local to avoid issues with your distribution packages.
 
-Additionally the following software is required to be able to build and install
+Additionally the following software is required in the host system to build
-xbps binary/source packages:
+and install xbps binary packages:
 
 	* GNU GCC C++
 	* GNU Make
+	* GNU Bison
 	* fakeroot
 	* wget
 	* libarchive (development package)

doc/SRCPKG_INFO

@@ -1,22 +1,3 @@
------------------------------------------------------------------------------
- REQUIREMENTS
------------------------------------------------------------------------------
-
-To be able to build packages from source the following software is required
-in the host system:
-
-	* GNU GCC C++
-	* GNU Make
-	* fakeroot
-	* wget
-	* libarchive (development package)
-	* perl
-	* sudo
-
-Super-user privileges are required as well, because all packages are built
-in a chroot (except the ones that are included in a virtual package to be
-able to build a minimal system for the chroot).
-
 ------------------------------------------------------------------------------
  HOW TO BUILD/HANDLE PACKAGES FROM SOURCE
 ------------------------------------------------------------------------------
@@ -28,7 +9,7 @@ level directory.
 
 If configuration file is not specified from the command line with the
 -c flag, it will first try to use the default location at
-/usr/local/etc/xbps.conf (or the installation prefix that was specified
+/usr/local/etc/xbps-src.conf (or the installation prefix that was specified
 to the make(1) command), and as last resort in the etc directory of the
 current directory.
 
@@ -59,7 +40,7 @@ installing packages you should use the install target:
 	$ sudo xbps-src install glib
 
 If the package is properly installed, it will be "stowned" automatically.
-``stowned´´ means that this package is available in the master directory,
+``stowned'' means that this package is available in the master directory,
 on which xpbs has copied all files from DESTDIR/<pkgname>.
 
 To remove a currently installed (and stowned) package, you can use:

doc/TODO

@@ -4,23 +4,6 @@ xbps-src:
    Something like ${sourceforge} to pick up any specified mirror on the list.
  * Fix -C flag while building packages via chroot.
 
-Packages:
- * Create /etc/issue.
- * Add a trigger for fc-cache.
- * Add a trigger to (un)register users/groups. Currently packages that
-   require user/groups use custom INSTALL/REMOVE scripts, which adds
-   a lot of duplicated work.
- * Add support to stop and restart package's OpenRC service while
-   removing and upgrading a package.
-   [PARTIAL: at pre-remove the services are stopped but not yet restarted]
- * How to handle kernel package upgrades? dpkg seems to keep previous
-   package and its initramfs, and a dummy package depends on the latest one.
-   I think this is the best option.
- * Fix initramfs-tools trigger for $pkgname != kernel.
- * Fix initramfs-tools 'update-initramfs -a'.
- * Fix HAL/PolicyKit for nonroot to be able to admin tasks.
- * Fix loadkeys(1) incorrectly loading the olpc keymap vs qwerty.
-
 xbps-bin:
  * Add support to install binary packages without any repository.
  * Add a flag to reinstall a package version that is already installed,
@@ -41,6 +24,4 @@ libxbps:
     taken into account yet]
 
 xbps-repo:
- * Add support to add only specified packages, rather than looking
-   at all files in a directory.
  * Add support for remote repositories, requires libfetch.