diff options
Diffstat (limited to 'README')
| -rwxr-xr-x | README | 19 |
1 files changed, 12 insertions, 7 deletions
@@ -32,16 +32,21 @@ or beta testing. The same applies to extra and extra-testing. linhes-dev contains the tools and scripts for a working development environment, but it is not a working development by itself. The script setup-env.sh will do all the work in creating a working development -environment. The script will download and install the required packages +environment. Get the script at: + http://linhes.org/repo/setup_env.sh +The script will download and install the required packages (from the current stable release) into a directory called build_root and create a script that can be used to enter the chroot. Because LinHES will support multiple architectures, setup-env.sh -requires an argument telling it which architecture to work with. Currently -i686 is the only working option, so that is the one I recommend you use. -For example running "setup-env.sh i686" will create a working i686 LinHES -development environment named build_root.i686. Setup-env.sh also creates an -empty directory structure called pkg_repo, this is used by kmsync.sh -(which will be discussed later). +requires arguments telling it which architecture to work with as well +as which repository (stable or testing) you'd like to develop on. +Currently i686 is the only working architecture option, so that is the +one I recommend you use. + For example running "setup-env.sh i686 testing" will create a +working i686 LinHES development environment named build_root.i686 using +the testing repos. setup-env.sh also creates an empty directory +structure called pkg_repo, this is used by kmsync.sh (which will be +discussed later). To enter the build root run (as root) the newly created script called enter_build_root.i686. The script will take care of the following things: |