Since this referred to a mac version, I can only assume it wasn't the first one :) I guess Pd was more easily accessible to Linux users that knew their way around, and that the "extended" project was a "CVS version" with extra stuff that you could build yourself. Another email talks about building it for windows that says "
to my great suprise, the pd-0.36-extended2 package off sourceforge compiles under windows with a minimum of effort" =>
https://lists.puredata.info/pipermail/pd-list/2003-03/010635.html . Please enlighten me on the birth of extended, I'd love to hear how it started, and also why it was referred to as "the CVS version".
"Now that the majority of the usability enhancements have gone
"mainstream," (yay! thanks, Miller!) I see little reason to make Mac
users use a forked version."
So yeah, I can now see that from its very inception, Extended started off as a 'fork' of some sort, but not aimed at a distinct evolutionary line, and more as a parallel development branch, aimed to facilitate the distribution of Pd and its main externals, and also serving as a testbed (as previously mentioned). So, ok, no, it wasn't just "Pd distributed with externals".
But some things are still unclear to me, like how things worked for Linux, for instance, when talking about "extended" Hans mentions "
0.37-test7 is in Debian already, along with a lot of externals from the CVS. The packages are called puredata, pd-externals, pd-cyclone, pd-osc, pd-zexy." reference:
https://lists.puredata.info/pipermail/pd-list/2003-10/014125.html - so, how would you install extended on Linux then?