Re: truce

[Christopher Rogers <slaxemulator@xxxxxxxxx>]

It looks like no one case about a source dvd that can be a tank replacement if tank goes down. Or tank on local lan. 

1) No rootfs.gz is used build chroot by default. Use packages instead.

2) Use sane basic packages. So no xorg or gtk in the default chroot. Some command line tools may compile gtk version if gtk is detected install but with no disable switch we can't stop it from building gtk version.

3) I don't want unneed depends install just cause it saves cpu on tank. Here are the list of packages tazwok installs into chroot:
linux-api-headers
glibc
binutils
gcc
busybox
ncurses
bash
bzip2
gawk
gettext
m4
make
patch
db
gdbm
zlib
perl
texinfo
autoconf
automake
lzma
tazpkg
tazwok
pkg-config
libtool
libpthread-stubs

This is what we need for chroot. Not everything.

On Fri, May 6, 2011 at 8:33 PM, Christopher Rogers <slaxemulator@xxxxxxxxx> wrote:

I wanted things to say the way they are. /home/slitaz/cooking/packages is for cooking packages. This way /home/slitaz/cooking/chroot can be remove once you unmount everything.

On Fri, May 6, 2011 at 8:25 PM, Indigo <pointofavailability@xxxxxxxxx> wrote:

As I struggle to understand all of this, all I meant is that it's
desirable to have the choice of using the current filesystem
(pressumable with changes, not from a package list), rather than
having to use the default rootfs.gz from the ISO -- but this is more
about installs, maybe, and gen-iso.  Agreed, though, a chroot is
definitely the way to go.

On Fri, May 6, 2011 at 1:20 PM, Christophe Lincoln <pankso@xxxxxxxxxx> wrote:
>
>> yes, the same package should be buildable on stable, cooking, or
>> custom rootfs.gz
>
> Exactly and this is not the case anymore since many receipt have been
> modified to work with new Tazwok without keeping backward compatibility.
>
>> -- makes sense for install, too, so one can use 'tazusb writefs' and
>> keep any customizations
>
> But for path, on a regular system all is build in /home/slitaz, if you
> use cooking it will use cooking package and create cooking ISO smae for
> stable. But if one want to cook or make ISO from stable using cooking
> stuff, it must create a chroot (path is not important) and work in it.
> Finally in the chroot you will also find slitaz stuff in /home/slitaz
>
> - Christophe
>
> ---
> SliTaz GNU/Linux Mailing list - http://www.slitaz.org/
>
>

---
SliTaz GNU/Linux Mailing list - http://www.slitaz.org/