I wanted things to say the way they are. /home/slitaz/cooking/packages is for cooking packages. This way /home/slitaz/cooking/chroot can be remove once you unmount everything.
On Fri, May 6, 2011 at 8:25 PM, Indigo <[email protected]>wrote: > As I struggle to understand all of this, all I meant is that it's > desirable to have the choice of using the current filesystem > (pressumable with changes, not from a package list), rather than > having to use the default rootfs.gz from the ISO -- but this is more > about installs, maybe, and gen-iso. Agreed, though, a chroot is > definitely the way to go. > > On Fri, May 6, 2011 at 1:20 PM, Christophe Lincoln <[email protected]> > wrote: > > > >> yes, the same package should be buildable on stable, cooking, or > >> custom rootfs.gz > > > > Exactly and this is not the case anymore since many receipt have been > > modified to work with new Tazwok without keeping backward compatibility. > > > >> -- makes sense for install, too, so one can use 'tazusb writefs' and > >> keep any customizations > > > > But for path, on a regular system all is build in /home/slitaz, if you > > use cooking it will use cooking package and create cooking ISO smae for > > stable. But if one want to cook or make ISO from stable using cooking > > stuff, it must create a chroot (path is not important) and work in it. > > Finally in the chroot you will also find slitaz stuff in /home/slitaz > > > > - Christophe > > > > --- > > SliTaz GNU/Linux Mailing list - http://www.slitaz.org/ > > > > > > --- > SliTaz GNU/Linux Mailing list - http://www.slitaz.org/ > >
