There is tazwok cook option to just cook a package but It just installs and then uninstalls so it would may need NO_CHROOT option to disable removing packages. Or check that chroot is not mounted to enable this.
I never trust building anything on slitaz without a chroot since some of build depends may end up removing programs that that it shouldn't. Mostly cause of busybox applets we forgot to added back into post_remove. I fixed most of this problem in coreutils and util-linux-ng packages thought. Also if you see $1 in post_remove this is cause we can remove packages with --root option. Its help to not screw up your chroot installl when not in the chroot. On Tue, May 10, 2011 at 10:31 PM, Christophe Lincoln <[email protected]>wrote: > On Tue, 10 May 2011 22:23:53 +0000 > Christopher Rogers <[email protected]> wrote: > > > You sayed that gawk is needed to build glibc. Thats the relation > > cause it rebuilds everything clean like linuxfromscratch does. > > And ? Your cookorder should place gawk cook after toolchain since it > build depends on the gcc, glibc, etc. Mabe this show a bug in tazwok > because it want to handle DEPENDS and BUILD_DEPENDS and got wrong > order. > > Gawk like gcc and other base apps are needed to build your toolchain > from sratch. > > Also this one of the things contributor dont want with tazwok, tazwok > will build all unbuilt packages if not yet done so one who just want to > test is lib paclage must wait untils a big part of the wok is build. > What a maintainer needs is just a cook tool that cook his packages > without having to rebuild half of slitaz from scratch before... > > - Christophe > > --- > SliTaz GNU/Linux Mailing list - http://www.slitaz.org/ > >
