Why do you want MCE build dependencies when building the kernel?
Because quite often when I am developing and testing some packages, I
will first do manual editing, building and copying binaries for N900 in
the chrooted environment.
# /usr/sbin/qemu-binfmt-conf.sh
# cd /var/tmp/Trunk_Testing-armv7el
# chroot .
# cd mce
# make
... then scp the binaries build on non-chrooted terminal which has
network access to n900 for testing
Once I am happy with that, I will usually do the patches and then run
local obs build for final testing before committing changes to obs server.
So now what happens is that if I do "local obs kernel build", it has
removed all mce related devel-headers and before I can continue with
that I must re-install all mce packages by doing a local obs build for mce.
I have worked around this now by collecting a huge list of packages
under "extra-pkgs" option in .oscrc
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.
What I would like to have is some kind of option "update existing rpm's
and install only a new dependencies" without uninstalling anything.
Mika
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
