[ Thread Index |
Date Index
| More lists.tuxfamily.org/slitaz Archives
]
Hi,
> It means several things.
> 1) I was blind;
> 2) I still use "cooking" "cook" environment OTHER than we have on
> cook.slitaz.org;
Normal, you work on your local wok and in this case with the undigest
wok. On Tank it is this setup. Tank run 4.0 but we cook the cooking
packages and the undigest one in 2 different chroot. For the undigest
cooker we have a standard cooking chroot but the wok-undigest is cloned
in /home/slitaz/wok.
On your local system you should have gtk+3 in the wok with all the new
dependencies also in it (last atk, pango, etc). But last atk, pango and
friends are not compatible with GTK 2 and the current version in
cooking. If you upgrade them in cooking it will break GTK 2.
> 3) info in the wiki (
> http://doc.slitaz.org/en:devnotes:new-tazwok-illustrated) CORRECT to
> my local "cooking" "cook", but WRONG for server "cook":
>
> quote from wiki:
> > For each package, if there exists an associated -dev package, it
> > adds to
> the dependencies
You are using cookutils NOT the old Tazwok, this wiki tutorial is out
of date, please refer to the cookutils docs in Hg or installed on your
system.
That said I think it is a very BAD idea to add gtk+3 in the cooking
wok. It will break everyting. Or you have to make atk3 atk3-dev, pango3
pango3-dev, etc, and make SURE it will not overwrite some current
packages such as atk, pango, etc needed by gtk+ (version 2).
I leaved gtk+3 in undigest because it is a huge migration and we should
do slitaz 5.0 with gtk+ 2 only. After that we can upgrade and then
rename all current atk, pango, gtk+ to gtk+2 since some applications
are not yet ported to the new gtk+3.
- Christophe
--
SliTaz GNU/Linux Mailing list - http://www.slitaz.org/