Tollef Fog Heen <[EMAIL PROTECTED]> writes: > * "Joel Baker" > > | I might argue, in the case of APIs, that it is more a case of "If you don't > | have time to do it right, how will you ever have time to do it over" - it > | becomes *very* hard to un-entrench bad API choices, a lot of the time. > > people seem to have the misconception that d-i is one big block of > code with common APIs inside. It is not. It is a bunch of loosely > coupled modules with little common API or code (except for debconf > interaction, that is). (Not necessarily pointing at you here.)
I suppose I had something like that misconception. Where can I read about the actaul construction of d-i?