2011/4/12 Anas Nashif <[email protected]>: > > On 6 Apr 2011, at 15:15, Mika Laitio wrote: > >> I have setted in my .oscrc >> build-root = /var/tmp/%(repo)s-%(arch)s >> >> If I first build mce locally with "osc build armv8el Trunk_Testing", I have >> in my build root all packages that were required for building the mce on >> /var/tmp/Trunk_Testing-armv8el >> >> But If I will after that build kernel locally again with same "osc build >> armv8el Trunk_Testing", osc will now install all additional dependencies >> required by the kernel build to this same /var/tmp/Trunk_Testing-armv8el >> directory. >> That's fine, but for some reason it seems also be removing all dependencies >> that were required by the MCE but are not required for the kernel build. >> >> ... >> warning: /etc/gconf/2/path saved as /etc/gconf/2/path.rpmsave >> deleting GConf-dbus-devel >> deleting dbus-devel >> deleting dbus-glib-devel >> deleting glib2-devel >> deleting libdsme >> ... >> >> Is there any method for preventing this? > > Why do you want MCE build dependencies when building the kernel? > The packages are removed from the chroot, but they are still cached locally > for the next MCE build, meaning you will not be pulling them again from the > repos. > If you want to jump straight to building without removing anything, you can > try --noinit option > > --noinit, --no-init > Skip initialization of build root and start with build > immediately. > > Anas > > >> I know that one solution is to configure in oscrc a package specific build >> roots, but as each chroot takes about 1 gb of harddrive, >> I would rather try to have just arch specific chroots that contains all >> non-conflicting build dependencies for many different pacakages >> simultaneously.
I use --clean, personally /Carsten _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
