-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29-07-10 14:23, Robert P. J. Day wrote: > > not wanting to jump into the main debate, but what is the > feasibility of somehow "excluding" a package or two from a task you're > trying to build? as i'm sure you're tired of hearing, most of the > time when i try to build a task, it's typically one or two packages > that don't build that cause the whole thing to fail. > > so would it be hard to add an "exclude" option to bitbake that would > allow one to, say: > > $ bitbake -x gnash beagleboard-demo-image > > there would clearly have to be some dependency processing which might > require yet other packages to be excluded, etc, etc. > > and if one had already attempted the initial build, the exclude > specifier would require bitbake to go back and remove any trace of the > broken package so it didn't try to still get dragged in when trying to > build the final task image. or something like that. > > has this ever been proposed? would it be hard? it would certainly > be a temporary solution to lots of failed builds.
Yes, making builds non-deterministic is an excellent idea! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFMUov0MkyGM64RGpERAvneAJ9SNhrX4r6mNFSiwEdqvWGs4RC+yQCfW1HC 02033OcVHj/OKGxn99n01IU= =62Jo -----END PGP SIGNATURE----- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
