>> That is in fact what we did for an experimental SB2-based SDK for Harmattan. >> There are even two perls, the ARM version and the x86 version (both are >> known as /usr/bin/perl.) They don't have to have similar configurations; the >> x86 side contains only selected tools and >> doesn't have to be updated so often.
> But a definite no to a tools distribution that we map to that's not > updated so often. It's a maintainability nightmare. Packages that are > being built should be built using tools that are from the OS they're > being built for or we're in for a world of hurt. Let me rephrase the first point. If you have perl from tools and there is no changes related to perl in system at all you do not need to update the tool but could update you target with other stuff very often. Once perl is updated tool is updated simultaneously and if you do not want to install it from scratch you just easily update the tool as you update the target. That is not the case for build system when you explicitly install build environment from scratch every time and they are the same always but quiet convenient for end user who need just update the system. Best regards, Vasily _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
