ok :). but for now i'm still using cook, i'm trying to work in an environment similar to tank;
>From "http://doc.slitaz.org/en:devnotes:new-tazwok-illustrated"; i read: #Up to now, when a package had both a dependency and build dependency, the #receipt looked like this: # #DEPENDS="pkgX" #BUILD_DEPENDS="pkgX pkgX-dev" # #Now this is enough: # #DEPENDS="pkgX" --> is it true for cook? # pkgY depend's on pkgX #DEPENDS="pkgY" #BUILD_DEPENDS="pkgY pkgY-dev pkgX pkgX-dev" # #Now this is enough: # #DEPENDS="pkgY" --> and what about this behaviour? Daniele On Fri, Jun 3, 2011 at 10:44 PM, Christopher Rogers <[email protected]> wrote: > I have been working on my-cookutils for the source dvd that will (i hope) > merge the cookutils and tazwok features together. I have added a TANK > variable option already for stuff that ideally just for tank. > > https://bitbucket.org/godane/my-cookutils > > Highlights of my-cookutils: > * Incoming folder support. This was what allow tazwok to remove older pa. > > * AUTO_PURGE_SRC support. This is disable by default but the feature is that > you can auto remove sources that are older then your packages. This helpful > in that you will know you only have the sources for your packages instead > just having all older versions too. Need to do cook gen-src before enable > this. > > * Build repo without build wok. This is need for source dvd and this will > allow no need to build anything if you just want repo of your cached > packages. > > * Tazwok mount binds. This is again for source dvd. It will mount bind > folders like tazwok does when TANK is not enabled. So cache will be in > /home/slitaz/cooking/cache and $chroot/home/slitaz/cooking/cache. There is a > if statement in my cook.conf to change $SLITAZ to /home/slitaz when TANK is > enabled and when disabled its /home/slitaz/$VERSION. > > * Support for COOK_OPT again. This is needed so we don't bulk repack sources > that need to be original sources in order for them to work. This is also so > we can stay compatiable with tazwok. > > * Support for LAN_MIRROR. This is again for source dvd but it would be nice > if users can get source from mirror.slitaz.org instead of WGET_URL first. > This is only cause we are going to have recompressed sources now on mirror > that will save bandwidth. Some people may want to get the recompress source. > But this is mainly for the source dvd mirror features so your users on your > local lan can get sources from your tank/mirror machine. > > Problems with my-cookutils: > > I still need to make incoming folder friendly to cooker.cgi. Cause otherwise > a full wok build could be in incoming but the process bar will think nothing > got build since only looks at packages folder. And i can't just add packages > and incoming numbers since packages and incoming could have the same > packages or newer/older version of the same package build in packages. We > need to keep the wok and cooked list in sync with each other or progress bar > would just will not be actuate. The good news is this is the only major bug > i think with my-cookutils repo. > > I hope this helps. > > On Fri, Jun 3, 2011 at 7:05 PM, Claudinei Pereira > <[email protected]> wrote: >> >> Hi Daniele, >> >> The doc for cookutils is: >> >> http://hg.slitaz.org/cookutils/raw-file/tip/doc/cookutils.en.html >> >> 2011/6/3 Daniele Guerrieri <[email protected]>: >> > Hi, >> > >> > the info contained in >> > http://doc.slitaz.org/en:devnotes:new-tazwok-illustrated are true also >> > for cookutils? >> > >> > is there a complete - up to date - cook guide? >> > >> > Daniele >> > >> > --- >> > SliTaz GNU/Linux Mailing list - http://www.slitaz.org/ >> > >> > >> >> >> >> -- >> www.claudineipereira.com >> >> --- >> SliTaz GNU/Linux Mailing list - http://www.slitaz.org/ >> > > --- SliTaz GNU/Linux Mailing list - http://www.slitaz.org/
