2011/5/31 Arjan van de Ven <[email protected]>: > On 5/31/2011 9:12 AM, Tomasz Sterna wrote: >> >> On wto 31 maj 2011 11:41:17 CEST, Sander van Grieken >> <[email protected] <mailto:[email protected]>> wrote: >> > What about a multi-arch RPM approach, where binaries for multiple >> > architectures are contained in a single RPM, but where only the arch >> > specific variant is installed? >> >> ***This is possible to do even now by abusing noarch.*** >> ***Just create a noarch package with binaries for all architectures inside >> and ln/copy binaries for current arch to correct places in postinst >> script.*** >> > > > guys.. this is madness. > > > Android builds your NDK binary multiple times, once for each architecture > you choose (x86, armv5, armv7 etc). > For MeeGo, the same will be true.... > just we have a way of distributing binaries that's slightly more finegrained > than the android model and our output of the build > ends up nicely split up, saving download time as well as disk space. > > > nothing to see... lets move on.
I assume you're talking about the idea of many architectures in one RPM as madness which I do agree with. Could you look at the original thread starter post? It is entirely okay to call the original thread starter madness, just wanted to make sure the original idea is not dismissed out of hand because of 'fat' RPMs getting proposed further down in the thread :) BR Carsten Munk > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > http://wiki.meego.com/Mailing_list_guidelines > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
