Re: Cookutils development

[Christopher Rogers <slaxemulator@xxxxxxxxx>]

Also what if the tank when down for good? The mirror/tank iso was a replace meant for tank/mirror in case it when down. Thats what i was trying to provide.

Anyway i the shakes calm down a bit. I have found out that slitaz-boot-scripts should have been add so /etc/init.d/crond start will work in tazwok chroot. I added it to SLITAZ_TOOLCHAIN. I never know how you get into chroot without having a session open or something. So i wouldn't know how to make a bot in the older tazbb either. 

You can't just do tazdev chroot && tazwok cook-commit --misssing --all or something. Doing tazdev chroot && echo "hello" doesn't work so how do you setup chroot for your build bot when chroot is not in session.

On Sun, May 8, 2011 at 12:03 PM, Christopher Rogers <slaxemulator@xxxxxxxxx> wrote:

You don't get it. I need to be able to compile the toolchain no matter what otherwise the mirror iso is dead. You say you keep in main the my mirror disk then you say we don't need to build a complete toolchain. You kill the whole point of it my mirror disk. By saying this your giving me the shakes.

The way you build the toolchain is the not the way the linuxfromscratch way does. And its never been a clean way at all by you. And we had problems cause of that.

All this is doing is cause me more stress and sleeping problems. 

On Sun, May 8, 2011 at 10:36 AM, Christophe Lincoln <pankso@xxxxxxxxxx> wrote:

> anyway. I do love the web interface by the way but thats it.

Thanks!

> You need to build everything from scratch or you better off just
> tazpkg converting debian packages in place of slitaz packages. Cause
> without a clean build system your better off going to get more
> problems in later on.

No, I'm rebuilding alll packages with our toolchain and with packages
builded with it. Until the full toolchain change we DONT nee to rebuild
everthing from scratch by startin with the so famous toolchain.

For example, if we had the resource you would likely rebuild all
packages on a regular basic to check they always build, In this case
also we dont need to rebuild toolchain each time from sratch, only if
it change.