void-packages/doc
Juan RP f1f34487e2 xbps-bin: added -f flag for remove target.
Now if any package is going to be removed and it's required by
other packages, it won't let you remove it unless -f is set.

Here's an example of how it looks like:

[juan@fedora-vm xbps]$ xbps-bin -r ~/testing-xbps remove glibc
WARNING! glibc is required by the following packages:

	zlib-1.2.3 ncurses-libs-5.7 gcc-libstdc++-4.3.2 e2fsprogs-libs-1.41.4
	cracklib-2.8.13 expat-2.0.1 ncurses-5.7 cpio-2.9
	module-init-tools-3.6 busybox-initramfs-1.13.2 udev-138 procps-3.2.7
	pam-1.0.2 dbus-libs-1.2.12 lzma-utils-libs-4.32.7 coreutils-7.1
	sed-4.1.5 grep-2.5.4 gawk-3.1.6 gzip-1.3.12
	bzip2-1.0.5 bash-4.0 less-424 gdbm-1.8.3
	groff-1.20.1 lzma-utils-4.32.7 dbus-1.2.12 proplib-0.3
	dash-0.5.4 findutils-4.4.0 util-linux-ng-2.14.2 initramfs-tools-0.92o
	file-5.00 diffutils-2.8.1 wget-1.11.4 man-db-2.5.3
	sysklogd-1.5 eject-2.1.5 shadow-4.1.2.2 sudo-1.7.0
	e2fsprogs-1.41.4 tzdata-2009a vim-7.2 upstart-0.5.1
	kernel-2.6.28.1 xbps-base-pkg-0.1 kbd-1.14.1

If you are sure about this, use -f to force deletion for this package.
[juan@fedora-vm xbps]$

--HG--
extra : convert_revision : eeb92925e51f11d5b3bf7e069ed4986ae5fb0c2d
2009-03-01 01:34:15 +01:00
..
BINPKG_INFO Rename prepost-{inst,rm} to just INSTALL/REMOVE. 2009-02-26 18:01:18 +01:00
BINPKG_REPOSITORY Changed XBPS_META_PATH to /var/db/xbps rather than /var/cache/xbps. 2009-02-14 23:21:12 +01:00
README xbps-src: require sudo to build packages. 2009-02-16 17:36:21 +01:00
SRCPKG_INFO xbps-src: require sudo to build packages. 2009-02-16 17:36:21 +01:00
TODO xbps-bin: added -f flag for remove target. 2009-03-01 01:34:15 +01:00

README

-----------------------------------------------------------------------------
 WHAT IS IT?
-----------------------------------------------------------------------------

xbps - xtraeme's build package system.

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. It's in spirit the same than GNU stow, but the files are just
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
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.

-----------------------------------------------------------------------------
 REQUIREMENTS
-----------------------------------------------------------------------------

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
xbps. You can get it at:

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
xbps binary/source packages:

	* GNU Binutils
	* GNU Bison
	* GNU GCC C++ (plus GMP and MPFR) development packages
	* GNU Gettext
	* GNU Make
	* GNU m4
	* fakeroot
	* ncurses (development package)
	* 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).

PLEASE NOTE THAT fakechroot or fakeroot-ng DO NOT WORK.

------------------------------------------------------------------------------
 HOW TO USE IT
------------------------------------------------------------------------------

Before using xbps, some required utilities need to be built and installed
into $(PREFIX); by default they are installed into /usr/local.
You can do this by issuing "make" and "make install" as root in the top
level directory. See the REQUIREMENTS section above for required packages.

Once the xbps distfiles are installed into prefix, you can start building
packages from source, add local repositories with binary packages, install or
remove them, etc.

If you are only interested in building/using packages from source, see the
SRCPKG_INFO file.

For information about binary packages, see the BINPKG_INFO file.

------------------------------------------------------------------------------
	Juan Romero Pardines <xtraeme@gmail.com>