I’m lazy, so my personal mantra is to modularize – and NEVER mix data with presentation as it were. The software itself is it’s own install, so that it is completely generic, and non-specific. This way if my company gets bought, for instance, I don’t have to rebuild a big package. Settings go in a seperate package – and as a general rule, even here I install individual settings in individual packages, so that, for instance, you might put bookmarks in their own package browser setting configurations in another, etc – again, so that if I have to change any specific setting, I can with a minimum of work. This is just like InstaDMG to me – the more you split it up, the more easily you can change it later. IF you know you’re going to install Firefox, plus the bookmarks, plus the browser configs over and over and don’t want to have to do three packages? That’s what mpkgs are for. B ut that’s just my opinion, YMMV.
.
Comments are closed