> Isn't the best way to do this is to try and have a configuration stage that
> includes/excludes key features from the run time version that get's
> installed ...
It's better to design everything in such a way that you can install the full
version, but autoloading is used to ensure that the code for the features
which are not used doesn't get 'require'd or 'use'd (so that is costs neither
memory nor start-up time). Jason has done a lot of work in this direction
I18n is a good example why this is a much better strategy. At a site in the
USA, there may be many, big English-speaking lists and a small Spanish-speaking
list. The i18n code is not needed most of the time, but when a request related
to the Spanish-speaking list is processed it is needed. With autoloading you
load the i18n code only when it is needed.