TGB is back with more interesting comments.
Thanks for your comments, TGB! Let me respond to a few:
Vendor-supplied DMGs are standard for distribution, however they are not standard for deployment.
You say that only because your deployment software doesn’t support deploying directly from a drag-n-drop disk image. I think this is a case where we should bow to reality — since a lot of software is distributed this way, your software deployment system should make it easy to deploy software distributed in this format.
Default settings are part of deployment. They simply are.
Most consumers seem to be able to purchase, install and use third-party software with the default settings as chosen by the vendor. We find that also to be the case in our environment — we don’t have to customize settings very often. But when we do, we have lots of available tools to do so. Not having to (re)package the software itself gives us more time to spend on adding value for our organization.
I’m completely comfortable packaging Flash by hand.
That’s great. So am I. But not every admin is, judging by all the packaging questions I’ve seen. More importantly, what’s the value of hundreds or thousands of admins repeating the same task, but perhaps doing it slightly differently? Let’s have the vendor do that work.
I don’t work in a rigid corporate environment.
Neither do I!
