> IMHO, a package should not ask anything. Not even
> where to put the package. There are existing
> standards where to put optional packages.
That's exactly right.
As far as configuration goes, there are principally two options:
a) central directory of configuration, for example a LDAP directory server
b) preconfigured, packaged and *non-interactive* packages, delivering:
- software
- configuration foundation: generic configuration file(s)
- site/company-specific modifications to that/those configuration file(s)
aka overlays
Both a) and b) can be managed centrally, however, in the case of a), there is
no way to guarantee the consistency of the operating system and the payload.
b) has several adantages over a), namely, the configuration is fully automated,
can be controlled and enforced with an iron fist (noone is allowed to log in
and modify a system's configuration, ever), and can be plugged into/uploaded
into a centrally managed software deployment server; additionally, since the
configuration comes as package payload, it can be kept track of and checked for
consistency via standard OS software subsystem mechanisms (ala `pkgchk`).
The missing piece is the software deployment server. The options are to either
develop one inhouse (ideal in my opinion and experience), or buy a commercial
product, such as Opsware.
This message posted from opensolaris.org
