Hi Lucas,
My workflow.
Background. I have usually small amount of free space on my root partition (50-200 MB), and even I lost a pair of files when free space become zero (and problems to non-root log in). Also I have partition (previously) used as home partition for frugal SliTaz-4.0. This partition in my fstab and auto mounted on boot time as /mnt/slitaz.
I have cooking wok: /mnt/slitaz/slitaz/cooking/wok (but better I write it as /path/to/wok).
I have chroot: /mnt/slitaz/slitaz/gtk3 (/path/to/chroot).
All SliTaz projects are here: /mnt/slitaz/slitaz/all-slitaz-hg.
I working under default user "tux", I only set password.
Let's begin.
I need to update some package.
I opened Sakura.
su; tazdev chroot /path/to/chroot
Open second tab in Sakura.
su; cd /path/to/chroot/home/slitaz/wok; mc
In Midnight Commander one panel with chroot wok, change second panel to /path/to/wok.
Copy package's folder with receipt, edit receipt.
Switch to first Sakura tab, execute 'cook packagename'.
Switch to mc to see sources, installed files, to edit receipt, description and so on.
Common debugging process.
When package builds well, I opened third tab in Sakura. Note, as tux user, not as root. Open mc and copy receipt and all the needed stuff back from chroot wok to regular wok (/path/to/wok). Exit mc.
Check my changes in wok: hg st
If I need to add files: hg add
(Hg adds all new files because I not specify file names).
If I need to add and remove files: hg addrem
(again not specify no one file).
Check files added and/or removed: hg st
(again).
Now important action. Update this local wok to the latest revision from hg.slitaz.org: hg pull -u
It may be no changes at all, or few changes to other packages, or anybody changed the same files as you (conflict).
Conflict resolving is beyond this small post. Go forth.
Why this action is important? Because of history should be continuous.
Now write commit description: hg commit
Text editor will open (using environment variable EDITOR) and you can write and save your message.
Push commit to server: hg push
That's all.
I only want to say, you previously need to edit your ~/.hgrc as described (somewhere) in the http://www.slitaz.org development corner, and add your real name (or nick), e-mail, and even hg password (if you need).
I wrote using smartphone now, so here any examples.