Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FR: Include PlistReader with Apps as part of .pkg recipes #172

Open
apizz opened this issue Oct 25, 2020 · 0 comments
Open

FR: Include PlistReader with Apps as part of .pkg recipes #172

apizz opened this issue Oct 25, 2020 · 0 comments
Assignees

Comments

@apizz
Copy link

apizz commented Oct 25, 2020

Describe the solution you'd like
This is a bit of an opinionated ask, but thought I would put it out there.

At present, when a DMG or an app that utilizes a Sparkle feed is dragged into Recipe Robot, when a .pkg recipe is selected to be created all that's included in the .pkg recipe is AppPkgCreator. The only output from this processor is version, but there is frequently other info - like LSMinimumSystemVersion - which would be useful for those admins that utilize non-munki recipes which don't automatically look at or collect this information because they require software deployment through a package. As a result, I would like to see PlistReader be added to acquire any and all applicable software keys, including:

  • CFBundleIdentifier
  • CFBundleShortVersionString
  • CFBundleVersion
  • LSMinimumSystemVersion

This way for example, if I as a munki admin don't create a .jss recipe with Recipe Robot that someone who comes along and uses my Recipe Robot .pkg recipe as a parent recipe that they can utilize this info. without having to create a separate PR to get this added to my .pkg recipe.

Describe alternatives you've considered
Manually adding these after the fact.

Additional context
Ultimately this isn't something I desperately need by any means. More that for those that use Recipe Robot to build all or the majority of their recipes that it would be best to ensure anyone who creates parent recipes from this that they are to take advantage of these keys & values that we know are important.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants