I think a script a that started out like this and add to your crond: tazwok chroot tazwok update-wok tazwok cook-commit --missing --forced exit
Please don't test on tank directly until you know this will work on tank without break stuff. Tank is becoming a magic box at this point. On Thu, May 5, 2011 at 8:54 PM, <[email protected]> wrote: > > For tazwok to work STOP making a fork. You will have to reverse alot > thats > > in the wok already. And its very tazwok compatible stuff. So are you > going > > to add in report functions and other things that tazwok needs to build > > packages. I don't think you will. > > > > Me and GoKhlaYeh worked very hard to make tazwok the way it is today. > Also > > we remove all the .pyo and .pyc files from packages. Are you going to > > remove > > them too in your packages? > > > > Tazwok is not broke. I know this. GoKhlaYeh knows this. Please don't > > reinvent the wheel when you have race car in front of you. > > Last year we had a tazbb which automagically built packages & flavors > updated in hg every 2 hours and gave us a web status page. > > It could cook any packages including nscd or glibc. > > Does your wonderfull buf free tools do it now ? > > -pascal > > > --- > SliTaz GNU/Linux Mailing list - http://www.slitaz.org/ > >
