Update README with some random and stupid comments.
--HG-- extra : convert_revision : 0aa3457561682eee9074bd28eac3bf6682bc75ed
This commit is contained in:
parent
000b040397
commit
227c4af4a4
31
README
31
README
|
@ -1,7 +1,15 @@
|
|||
xbps - xtraeme's build package system.
|
||||
|
||||
It is a simple build package system that uses Xstow to allow packages
|
||||
to be available at a master directory.
|
||||
It is a simple build package system that installs packages inside of
|
||||
a chroot in a destination directory. Once the package has been installed
|
||||
into this directory, you can make it appear/unappear at the master directory
|
||||
at any time.
|
||||
|
||||
xbps has been designed for Linux, and for the moment I'm not interested on
|
||||
make it work on any other random OS. I've been a NetBSD developer for some
|
||||
years and I do not want to come back... also the experience has helped to
|
||||
me to start xbps and not to use pkgsrc, which is very portable but also
|
||||
not so fast.
|
||||
|
||||
xbps uses proplib, a property container object library and it's almost the
|
||||
same one available for NetBSD. Be sure to have it installed before using
|
||||
|
@ -9,6 +17,8 @@ xbps. You can get it at:
|
|||
|
||||
http://code.google.com/p/portableproplib/
|
||||
|
||||
I'm also the human maintaining the portable proplib package.
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
HOW TO USE IT
|
||||
------------------------------------------------------------------------------
|
||||
|
@ -24,15 +34,20 @@ If XBPS_CONFIG_FILE is not set or specified from the command line with the
|
|||
-c flag, it will first try to use the default location at
|
||||
/usr/local/etc/xbps.conf, and as last resort in current directory.
|
||||
|
||||
Once that you read the "xbps.conf" file and configured it, you can start
|
||||
installing packages by using the command:
|
||||
To avoid problems with libtool and configure scripts finding stuff that is
|
||||
available in the host system, you should install the xbps-base-chroot package
|
||||
as the first thing once the xbps.conf file is ok.
|
||||
|
||||
Once xbps-base-chroot has been installed, all packages that aren't part
|
||||
of this will require root permission to be used in the chroot. Think about it,
|
||||
all is done at the chroot, less stuff to break with missing dependencies and
|
||||
incompatibilities found by the configure scripts.
|
||||
|
||||
Let's explain some more about the targets that you can use. To start
|
||||
installing packages you should use the install target:
|
||||
|
||||
$ xbps.sh install glib
|
||||
|
||||
While installing your first package, if xbps couldn't find the Xstow program
|
||||
specified at the configuration file with XBPS_XSTOW_CMD, the Xstow package
|
||||
will be installed and "stowned".
|
||||
|
||||
If the package is properly installed, it will be "stowned" automatically.
|
||||
``stowned´´ means that this package is available in the master directory,
|
||||
on which xpbs has copied all files from DESTDIR/<pkgname>.
|
||||
|
|
Loading…
Reference in New Issue