Software Dependency

Hi James,

You could make a policy for JRE and other dependencies that runs only on computers that do not have it. So that policy would be scoped to a smart group. Then you could call those policies in the advanced unix command section of the application policy that might require dependencies with a custom trigger supplied in each dependency policy. The trigger(s) can be called with

jamf policy -trigger <jre_custom_triger>;jamf policy -trigger <other_dependency_trigger>

and so forth. The triggers will run the policy only if they are applicable in that policy based on their scope so as to not run unnecessarily.

Hope that might help.

-Brad

We usually use a collection of smart groups as well. For example, if the Mac needs app, which in turn needs JRE, we would create a smart group that finds computers that don't have JRE, and scope JRE to it. Then another smart group that has JRE but doesn't have the other app, again deploying the app to that group.

That being said, another approach could be to deploy JRE to all Macs regardless so it is always there if needed. We do this with printer drivers, so if a client is using HP printers, we deploy the HP driver pack, regardless whether we are adding the printers to every Mac. It makes deploying the printer later a much easier task.

Last thought would be to just make a policy that deploys both packages, making sure JRE is first. If it's an isolated requirement, this would be easier than making smart groups etc.

Sounds like a candidate for a feature request.

You should be able to tell Casper that pkg Foo requires pkg Bar, so that any time Foo is installed by Casper, it also ensures Bar is installed.

This is where the model of "find machines that match condition X and do Y do them" falls down as a strategy for managing software installations. It's useful in some scenarios, but doesn't fit them all.

Its a great idea, and is very similar to this old request (Under Review now for some time): https://jamfnation.jamfsoftware.com/featureRequest.html?id=83

@gregneagle wrote:

Sounds like a candidate for a feature request. You should be able to tell Casper that pkg Foo requires pkg Bar, so that any time Foo is installed by Casper, it also ensures Bar is installed. This is where the model of "find machines that match condition X and do Y do them" falls down as a strategy for managing software installations. It's useful in some scenarios, but doesn't fit them all.

The "requires" feature in Munki is one of those things I'm going to miss when I leave this gig.

Using a diverse assortment of tools was a great opportunity to identify some areas that need improvement (to each of the tools).

+1 voted up

Don

Six years later I find myself searching for a way define dependencies between pkg's in Jamf Pro and stumbled on this thread.

Any news on this?

Unfortunately the old FeatureRequest links don't work anymore and I can't find anything on the new ideas.jamf.com site.

I think this is the feature request post you're looking for: https://www.jamf.com/jamf-nation/feature-requests/3696

Ahhh, one of the old one's that will never get prioritized... I have a'many of those! 😕😕

These URLs https://www.jamf.com/jamf-nation/feature-requests/3696 and https://jamfnation.jamfsoftware.com/featureRequest.html?id=83 seem dead for me. It would be nice to know if this feature request is still under consideration or is being permanently ignored at @benducklow suggests. About 7 years now. That looks kinda' bad.