On 02/28/10 02:39 PM, Peter Tribble wrote: > On Thu, Feb 25, 2010 at 7:23 PM, Shawn Walker<swalker at opensolaris.org> > wrote: ... >> A better option than a tarball would be to use the pkg tools to dynamically >> create a pkg(5) package and install that. That has the added benefit of >> being able to verify the contents of the install including the "splatted" >> contents. > > That's a terrible option. If installing an IPS package was a reasonable > solution to the problem, it would be done that way to start with.
Dr. Terrible doesn't think so :) > The applications thus installed may have their own builtin management > and update mechanisms, which native packaging would conflict with; Then the packaging wasn't done right or is there is some bit of packaging functionality that isn't yet implemented. > they may be designed to be modified after install; they may be highly > dynamic (such as a mysql database); they may be fully integrated > into an existing application and configuration management system; > they may contain highly system and context specific files. Not all > applications (especially in-house or legacy ones) can even be managed > sanely by packages. Which doesn't preclude making the recommended method importing a tarball and creating a package. Tarballs should be the option of last resort. Packages will always give an administrator a more reliable way to ensure consistent, correct installations. Cheers, -- Shawn Walker
