Skip to main content
Question

I made something else for you, launchd Package Creator

  • May 21, 2019
  • 9 replies
  • 66 views

Forum|alt.badge.img+19

Fresh off the heels of DockBuilder, I've pushed something else I've been working on to GitHub for the community.

launchd Package Creator is a utility that allows you to easily create a .pkg containing a LaunchDaemon or LaunchAgent, and a target script of your choosing. The target script is also packaged, so nothing else is required on the Mac.

This is a pre-release, so be aware that you might encounter some bugs, and there are not a ton of options right now either. Like always, use it, or not, your choice.

9 replies

Hugonaut
Forum|alt.badge.img+15
  • Esteemed Contributor
  • May 21, 2019

Again! Nice Ryan! Going to save a lot of people a lot of time, very nice. Thank you!


Forum|alt.badge.img+10
  • Valued Contributor
  • May 21, 2019

As someone that has to reference daemons every time I need a new one, this should help save some time. Thanks!


Forum|alt.badge.img+5
  • Contributor
  • May 21, 2019

This is nice, I like this. It could really make people's life alot easier to just make a package. Also gives me ideas.

We use python to write both the LaunchD file and the BASH or Python script it calls. That way I never have to re-package anything. But, seeing this, makes me thing I could write something that would push the python up to JAMF through the API.


Forum|alt.badge.img+5
  • Contributor
  • May 24, 2019

Najs :)


Forum|alt.badge.img+13
  • Contributor
  • May 24, 2019

This is great thanks!


mvught
Forum|alt.badge.img+9
  • Contributor
  • May 24, 2019

Perfect mate, thanks a lot for sharing


Forum|alt.badge.img+19
  • Author
  • Contributor
  • May 25, 2019

Keep an eye out. A couple more features will be added Tuesday or Wednesday.


Forum|alt.badge.img+10
  • Contributor
  • May 28, 2019

Thanks Ryan
Are the built packages automatically signed? See this coming handy used in conjunction with the --eraseinstall command.


Forum|alt.badge.img+19
  • Author
  • Contributor
  • May 28, 2019

@tjhall They are not signed. You could sign it yourself using:

productsign --sign "{your_identity}" original.pkg signed.pkg

I could maybe work in an option to sign the .pkg using your own cert in a future release.