summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorPanu Matilainen <pmatilai@redhat.com>2011-04-04 14:39:19 +0300
committerPanu Matilainen <pmatilai@redhat.com>2011-04-04 14:39:19 +0300
commit7e91fb7370433484b10e54790d97a731656b68ec (patch)
tree05a99da97f138b1d36161561f05fd937cbc9eb57 /INSTALL
parenta81d933cc3b997c7f46acd4a3faff26ce2edc8b7 (diff)
downloadlibrpm-tizen-7e91fb7370433484b10e54790d97a731656b68ec.tar.gz
librpm-tizen-7e91fb7370433484b10e54790d97a731656b68ec.tar.bz2
librpm-tizen-7e91fb7370433484b10e54790d97a731656b68ec.zip
Update INSTALL a bit, include blurb about the test-suite + fakechroot
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL23
1 files changed, 7 insertions, 16 deletions
diff --git a/INSTALL b/INSTALL
index bde9efab3..96ddbdb9b 100644
--- a/INSTALL
+++ b/INSTALL
@@ -161,20 +161,12 @@ and then install with:
make install
-If you wish to make a tarfile of the binaries so that you may easily
-install on machines with OS package managers other then rpm (ed note:
-what about putting gzip and bzip2 in the tar, modifying the
-/etc/rpmrc?):
+Rpm comes with an automated self-test suite. The test-suite relies heavily
+on fakechroot (https://github.com/fakechroot/) and cannot be executed
+without it. Provided that fakechroot was found during configure,
+it can be executed after a succesful build with:
- make tar
-
-when installing. If you do install from a tarball, you will need to do
-something like
-
- mkdir /var/lib/rpm
- rpm --initdb
-
-to initialize your rpm database.
+ make check
Finally, if you wish to prepare an rpm source tar ball, you should do
@@ -311,13 +303,12 @@ Pro would want `i586pro' over `i586-pro', but it does make parsing
this filename by other programs a bit more difficult.
-GPG/PGP/PGP5
-------------
+GPG
+---
To use the signing features of rpm, you will need to configure certain
rpm macros in ~/.rpmmacros:
- %_signature gpg
%_gpg_name <GPG UID>
%_gpg_path %(echo $HOME)/.gnupg