simplepkg 0.4.9pre1

git-svn-id: svn+slack://slack.fluxo.info/var/svn/simplepkg@4 04377dda-e619-0410-9926-eae83683ac58

1 files changed, 11 insertions, 4 deletions

diff --git a/README b/README
index 1c6eefc..50b0e9d 100644
--- a/README
+++ b/README
@@ -50,6 +50,8 @@ by the following commands:
    - jail-upgrade: upgrade all or some of the jails/installations 
    - jail-update: update all configuration files of a template
    - rebuildpkg: rebuild a package based on its /var/log/packages entry
+   - simplaret: package retrieval tool
+   - createpkg: donwload, compile and package creationg script based on http://slack.sarava.org/slackbuilds
 
 Simplepkg configs are placed at /etc/simplepkg. Templates are .template files containing an one-by-line
 package list. A template can be something like this:
@@ -211,12 +213,12 @@ use simplaret and not swaret as the package retrieval tool.
 As another example, to create an slack 10.1 installation (assuming your /etc/simplepkg/repos.conf with
 the right configuration), just type
 
-  VERSION=10.1 mkjail minha-jaula template-servidor
+  VERSION=10.1 mkjail my-jail server-template 
 
 Different archs can be used too. If you have a x86_64 system and wants to install a slack 10.2
 in a partition, try something like
 
-  ARCH=i386 VERSION=10.2 ROOT=/mnt mkjail hda2 meu-slackware
+  ARCH=i386 VERSION=10.2 ROOT=/mnt mkjail hda2 my-slackware
 
 Note that the templates are arch and version independent, as they just contain package names,
 configuration files and scripts. For this reason, the commands templatepkg, metapkg, lspkg and
@@ -230,8 +232,8 @@ By this way, doesn't matter which versions and archs each of your jails has, jai
 the same since your patches are sorted by arch an version, as explained in simplaret documentation
 found at http://slack.sarava.org/node/17.
 
-Auxiliar application: rebuildpkg
---------------------------------
+Auxiliar applications: rebuildpkg and createpkg
+-----------------------------------------------
 
 Simplepkg comes with an additional helper tool that recover installed packages which the original
 .tgz file was lost. The command rebuildpkg rebuilds a package from their entry in /var/log/packages.
@@ -242,6 +244,11 @@ As an example,
 rebuilds the coreutils package using the files, scripts and metainformations stored in
 /var/log/packages/ and /var/log/scripts/.
 
+If you want to build you own packages using the scripts available from http://slack.sarava.org/slackbuilds,
+use the createpkg script:
+
+  createpkg package-name
+
 Source
 ------