Only moments ago, Bill Studenmund wrote:
> I think the idea of knowing how big the sets are is a good one. I think
> the idea of embedding the size into the application is not so good. I
> don't think it will scale at all well.
> 
> I think what would work better is .... Include a file with
> the sets that contains all the sizes, a manifest if you will. This file
> could also include what sets actually are there (x sets, what multitude of
> kernels are present), sizes, and other info we want.

Sure - by "the data built into sysinst" I didn't mean specifically
implemented as a C array initializer or anything; "sitting in a file
included in the distribution that sysinst knows to look in" serves the purpose
just fine.  :)

-Chap