On Mon, Feb 28, 2011 at 16:57, Phil Blundell <[email protected]> wrote: > On Mon, 2011-02-28 at 13:26 +0000, Otavio Salvador wrote: >> -PACKAGE_ARCHS = "all any noarch ${TARGET_ARCH} ${PACKAGE_EXTRA_ARCHS} >> ${MACHINE}" >> +DISTRO_ARCH = "${TARGET_ARCH}-${DISTRO}" >> +MACHINE_DISTRO_ARCH = "${MACHINE_ARCH}-${DISTRO}" >> +PACKAGE_ARCHS = "all any noarch ${TARGET_ARCH} ${PACKAGE_EXTRA_ARCHS} >> ${DISTRO_ARCH} ${MACHINE_DISTRO_ARCH} ${MACHINE}" > > This seems a bit weird. Any given package feed (or TMPDIR) is, more or > less by definition, going to correspond to a single DISTRO so I can't > see any situation in which these extra archs would be useful. What's > the use-case for this?
We have a set of products that reuse a common distro definition but has different needs on a small set of packages. To avoid having them all rebuild we set those to DISTRO_ARCH and the ones that depends on machine and distro to MACHINE_DISTRO_ARCH avoiding a lot of rebuilding and CPU time. -- Otavio Salvador O.S. Systems E-mail: [email protected] http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
