You say tank is not ment to have everything build from scratch. Problem is we do build every package from scratch when start the new cooking. So again cookutils will just be cloning tazwok but simplify it.
The best idea is to allow it to be simple and as powerful has tazwok is now. I'm starting my work on it now: https://bitbucket.org/godane/cookutils/ All changes are in testing branch so i can merge default branch when you get it up on hg.slitaz.org. I have svn and git support added into cook now. Also i have a cooking branch for my-wok: https://bitbucket.org/godane/my-wok I hope this helps. On Thu, May 5, 2011 at 1:22 PM, Eric Joseph-Alexandre <[email protected]>wrote: > Le Thu, 5 May 2011 13:14:36 +0200, > Christophe Lincoln <[email protected]> a écrit : > > > > > Hi, > > > > > > > It must stay a KISS tool, > > usable by everyone easily, unbloated. > > > +10 > > > AND the cookutils will cook package but not do the all diner for you, > > we need quality receipt and for speacial case, it is not to the build > > tool to adapte it self, but to the receipt to be adapted. > +100 > > > ... You and Gokhlayeh would have been the first knowing these tools > > because effectively there will replace Tazwok on Tank, and I'm sure > > you know why. Tazwok is no more a slitaz philosophy tools but a > > complex Debian alike tool... Ok it's the only way to get a full > > system rebuild from sratch and in one command. But this is not the > > need of Tank and not the need of most SliTaz Developers. > > > +1000 > > > > > - Christophe > > > +Eric > > --- > > SliTaz GNU/Linux Mailing list - http://www.slitaz.org/ > > > > > --- > SliTaz GNU/Linux Mailing list - http://www.slitaz.org/ > >
