Hi,
the last time when I made an installer I simply included every needed file in my installer and set their appropriate expected locations (for example, I remember using /Applications/Max5/Cycling '74/third-party/MyStuff for externals etc). However, it turned out that the installer caused more trouble than benefits, so my personal opinion is that for Max-externals the best way of installing them is the manual one. Here are my two main reasons to consider:
- if you release your externals in a non-commercial way (eg. GPL or Creative Commons), the following scenario is quite likely to happen: software A and software B use your externals. You, and software A and software B all make their installers. Now, when an user installs at least two of these (let's say, your original external AND software A), the user would end up with two instances of the same external (and there's no way to tell Max that the 'original' is the one located in folder xxx) or worse: software A can easily overwrite your external with a probably older version of the same stuff. This scenario is constantly happening with my externals and independent projects using them...
- Creating a good installer for a Max external requires a lot of effort (to make sure that everything goes to its appropriate place, that nothing gets overwritten by your installer that is not supposed to get overwritten or, for example, that the XMLs containing the objects in the refdocs of Max 5 will be modified just as expected). If you have the time for this, fine. But If you don't/can't put this effort, your installer might simply erase/overwrite other third-party externals or break the refdocs structure etc. etc. etc.
To tell the truth, I have never seen an installer for any Max project that at the end of the day would have saved me time (if compared to the simply 'copy everything to the appropriate folder' approach).
Just my 2¢...
Ádám