tech-toolchain archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Sets, subsets, syspkgs, and MK*
On Wed, Dec 16, 2009 at 04:39:33PM +0000, Quentin Garnier wrote:
> What you propose essentially means maintaining about any combination
> of those MK/USE settings. So yes, it is complicating, and even done
> right, I'm sure it will turn out to be a lot of work, and
> unfortunately, not just for you.
isn't it correct release engineering to ensure that all combinations of
MK variables are regularly built and tested? it's what, only ~2^40
different combinations? :)
--
Aaron J. Grier | "Not your ordinary poofy goof." |
agrier%poofygoof.com@localhost
- References:
- Re: Sets, subsets, syspkgs, and MK*
- Re: Sets, subsets, syspkgs, and MK*
- Re: Sets, subsets, syspkgs, and MK*
- Re: Sets, subsets, syspkgs, and MK*
- Re: Sets, subsets, syspkgs, and MK*
- Re: Sets, subsets, syspkgs, and MK*
- Re: Sets, subsets, syspkgs, and MK*
- Re: Sets, subsets, syspkgs, and MK*
- Re: Sets, subsets, syspkgs, and MK*
- Re: Sets, subsets, syspkgs, and MK*
- Prev by Date:
Re: Sets, subsets, syspkgs, and MK*
- Next by Date:
Re: Sets, subsets, syspkgs, and MK*
- Previous by Thread:
Re: Sets, subsets, syspkgs, and MK*
- Next by Thread:
Re: Sets, subsets, syspkgs, and MK*
- Indexes:
Home |
Main Index |
Thread Index |
Old Index