Untill ther all whent well. I use sandbox=/home/slitaz/cooking/sandbox and mounted /home/slitaz
> # By default MAKEFLAGS is set to number of cpu +1, but on a server > # providing other services than cook it's better to use number of > # cpu. (important) > sed '/^MAKEFLAGS/ s/+1//' -i /etc/slitaz/tazwok.conf Ok but file is /etc/tazwok.conf (should effectively move to /etc/slitaz) > # Create the cooking chroot and cook the last version of tools > # (important) > tazpkg recharge > tazwok chroot > # Now you are in the cooking environnment (order is important) > tazwok cook libtaz > tazwok cook tazwok-experimental > tazwok cook tazpkg > tazwok cook tazchroot > exit When you mean create a cooking chroot, like usual ? tazdev gen-chroot ? And then you mean 'tazdev chroot' ? Tazwok chroot doesn't exist... > # Make tazpkg use the local repository. > tazpkg setup-mirror /home/slitaz/experimental/packages > tazpkg add-undigest > experimental-incoming /home/slitaz/experimental/packages-incoming > > # The packages you just cook are into packages-incoming, > # we need them so temporaly prioritize packages-incoming repository. > echo experimental-incoming > /var/lib/tazpkg/priority > > # Install the new version of tools. (libtaz first is important) > tazpkg get-install libtaz > tazpkg get-install tazpkg > tazpkg get-install tazwok-experimental > tazpkg get-install tazchroot > > # Remove the priority on experimental-incoming > rm /var/lib/tazpkg/priority > > # The sandbox is setted up :) - Christophe --- SliTaz GNU/Linux Mailing list - http://www.slitaz.org/
