On Tue, Feb 03, 2009 at 07:48:38PM -0500, Jim Dunham wrote:
> Is there an IPS packing developers guide, must like the SRV4 packaging
> guide?
I'm not sure there's anything that covers dependency analysis in any
detail, but you should start here:
http://opensolaris.org/os/project/pkg/documents/Nov2008/
>>> Case in point, the AVS packages provided SMF manifests which contain
>>> specific service dependencies, but these dependencies, and others are
>>> modified in real-time, based on the output of certain run-time utilities,
>>> like 'clinfo' - display cluster information. AVS is Solaris Cluster
>>> aware,
>>> and vice-versa, and if clustering is enabled, it makes sense for SMF to
>>> control service dependencies, in lieu of the old run-level scripts.
>>
>> I'm not sure I understand this. You're delivering services which have
>> dependencies on each other, but are suggesting that we don't pay attention
>> to them? Does nws-ii depend on nws_sv or doesn't it? From reading the
>> manifest, it does not appear to be an optional dependency.
>>
>> Butf SUNWii and SUNWrdc don't depend on SUNWspsv through their services,
>> then how do they depend on SUNWspsv at all? The service dependencies were
>> the ones you called out when first filing the bug.
>
> AVS dependencies are presently fixed, and non-changing. At times in the
> past, they were modified based on the results of 'clinfo', as a means for
> AVS and Solaris Cluster's dependencies and milestones to synchronize better
> at system startup and shutdown time.
Okay, so I'm back to not understanding why you're objecting to recording
dependencies in the package that are defined by SMF.
> Where is the value for IPS to have awareness of something that SMF already
> manages?
As I said before, pkg(5) doesn't do any dependency analysis on package
installation -- that's purely static. All we're talking about here is the
procedure for putting dependencies into the packages in the first place,
prior to and during publication.
We want to record the dependencies in the packages so that when the
packages are installed, the software will work, because all its
dependencies are present. This is the case for ELF dependencies, SMF
dependencies, dependencies in shell scripts, etc. Some of those we can
determine programmatically, though we may not presently. Others we have to
provide manually.
If we had no automatic dependency analysis and resolution prior to
publication time, we'd have to do it all manually, or no package would have
any dependency information. Or we'd have the situation we have today in
the Solaris WOS, where most packages provide useless dependency information
because it's been copied from some other, unrelated package.
Or are you suggesting that SMF should note that a dependency is missing and
attempt to download an install the package that provides it before bringing
the service up? Or that the dynamic linker do the same if it finds a
library missing?
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
