Re: Iceberg Package installing into /tmp by default?
Re: Iceberg Package installing into /tmp by default?
- Subject: Re: Iceberg Package installing into /tmp by default?
- From: Greg Neagle <email@hidden>
- Date: Tue, 4 Jan 2011 11:42:25 -0800
On Jan 4, 2011, at 11:22 AM, Hirtle, Clif wrote:
> Dummy Question #2:
> If we are all creating packages for common applications like these (and
> assuming no custom org-specific settings), is there not a more effective
> means of crowdsourcing our package efforts? I am aware of the Manifest
> Destiny project, but seems like there might be value in sharing/vetting
> the same Office 2010 installation being custom created across 500
> different organizations at the same time.
All the more reason to move your customizations into a separate package -- it removes the need to create modified vendor packages. Then you can share your customizations with others without having to worry about distributing commercial software.
This is why repackaging commercial applications is such a terrible thing. Not only is it time-consuming and error-prone, but it's very difficult to share your work. Further, it makes vendor support more difficult, because your repackaging effort may introduce issues that don't occur when the software is installed directly from the unmodified vendor package.
-Greg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden