On Tue, May 10, 2011 at 10:33 AM, Christopher Rogers
<slaxemulator@xxxxxxxxx> wrote:
I'm keeping tazwok standard in my wok otherwise you brake the cookorder..txt file. That is needed for my source dvd to work and make cause repos.
Also Goklayeh will not like tazwok to break cause he as 4.3 branch. He has a lot stuff he was going to add and now i don't know if he will come back cause of cookutils. You will break the work he worked very hard to get working.
So a fork of the wok branch is the only way for now.On Tue, May 10, 2011 at 8:38 AM, Christophe Lincoln
<pankso@xxxxxxxxxx> wrote:
Hi all,
As you might know the way deps and build deps are handled have change in
new tazwok compared to tazwok 3.0 and lloking to the general discuss
about tazwok and thinks we need standards. The other BUG is that Tazwok
have modified way we work but documentation have never been updated...
http://doc.slitaz.org/en:cookbook:receipt
Now he is a resume and what I think we should use as standards after 5
years of Slitaz. Say we have a package with more build deps than
because because it gtk gui is splitted into a separate packages.
Package also need Perl at runtime but not to build:
1. Old tazwok: absolutly no automatism but we have redudency:
DEPENDS="libusb pcre perl"
BUILD_DEPENDS="libusb libusb-dev pcre pcre-dev gtk+ gtk+-dev"
2: New tazwok: all is automatic, all deps are also installed as build
deps and it scan DEPENDS to install all -dev packages (ie libusb-dev).
In this case it will also install perl witch is not needed to build:
DEPENDS="libusb pcre perl"
BUILD_DEPENDS="gtk+ gtk+-dev"
3. Proposal standard: Minimum automatism but remove redudency since
they are implicit, you need libusb if libusb-dev is in build dep:
DEPENDS="libusb pcre perl"
BUILD_DEPENDS="libusb-dev pcre-dev gtk+-dev"
Any better suggestion ? Comments ?
- Christophe
---
SliTaz GNU/Linux Mailing list - http://www.slitaz.org/