On Fri, 2011-01-28 at 09:39 +0200, Sivan Greenberg wrote: > Uh-ha! So this seems closest to the deboostrap approach. Thanks Timo, > I will give this a try. So what essentially happens here is that the > spec file is for a package that pulls in all the dependencies and > installs them into the target build folder of the package? >
The spec is used to get the build started and getting some things already available in the chroot (in this case zypper, nano and ssh client). This method is basically taking advange of the way obs local builds work since it creates a chroot where local build happens. If you don't need to move the chroot anywhere you could use 'osc chroot [target]' In addition what I put in the wiki you probably want to install something to the chroot. to do that you need to define repos something like 'zypper ar http://[repo url] some-repo && zypper ref' and then install whatever you need e.g. "zypper install pattern:meego-development-tools" -Timo > -Sivan > > On Fri, Jan 28, 2011 at 9:10 AM, Timo Härkönen <[email protected]> > wrote: > > On Thu, 2011-01-27 at 12:38 +0200, Sivan Greenberg wrote: > >> How would you use the kickstart file to create a chroot? Is there a > >> doc on the wiki for that? > >> > > > > dunno about .ks files but you can use obs local build to make a chroot > > for you. > > > > http://wiki.meego.com/User:Timoph > > > > Play carefully with it :) > > > > -Timo > > > >> Thanks, > >> > >> -Sivan > >> > >> On Thu, Jan 27, 2011 at 3:11 AM, Luis Araujo > >> <[email protected]> wrote: > >> > kickstart files? > >> > > >> > On 01/26/2011 06:51 PM, Sivan Greenberg wrote: > >> >> > >> >> Hi List, > >> >> > >> >> Going over this doc: > >> >> http://wiki.meego.com/SDK/Docs/1.0/Building_a_MeeGo_chroot_on_Linux , > >> >> and if I follow the instructions right, you must loop mount the image > >> >> to have a chroot directory tree by copying it from the image. Now, if > >> >> the image is not current you need to then update the chroot which can > >> >> be a good thing if you want to test upgradability or bad if you want > >> >> to get started without another time consumin phase, especially if you > >> >> are on a limited resources SOC or a limited bandwidth environment, or > >> >> both. > >> >> > >> >> Are there any prospects to have a tool like debootstrap for MeeGo? I > >> >> am also curious if the same approach is used to create chroots for the > >> >> build infrastructure and/or the automated testing infra? > >> >> > >> >> Many thanks, > >> >> > >> >> -Sivan > >> >> _______________________________________________ > >> >> MeeGo-qa mailing list > >> >> [email protected] > >> >> http://lists.meego.com/listinfo/meego-qa > >> > > >> > _______________________________________________ > >> > MeeGo-qa mailing list > >> > [email protected] > >> > http://lists.meego.com/listinfo/meego-qa > >> > > >> _______________________________________________ > >> MeeGo-qa mailing list > >> [email protected] > >> http://lists.meego.com/listinfo/meego-qa > > > > > > _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
