Home → Feedback →

Make GPG Suite installer autopkg friendly?

• Edit

davidcwest

21 Jan, 2015 02:53 PM

Just an idea and really know idea if we as a company would do this or not, but thought came to my head today. Will you still have a donation option once the paid for version is out. I know you advice against compiling for yourself, but say someone or some company was compiling everything for themselves from git, would there still be an option to donate?

At the moment we push out all our application updates with Casper Suite, and this has caused some issues for us with GPGTools as it installs as root and other issues, I was wondering if either you might consider making your software in a way that would work for autopkg recipe's? Another option is we compile directly on each machine this is needed. If we went that route I think we would still want to contribute for all your hard work :)

1. 1 Posted by Mento on 26 Jan, 2015 11:21 PM

   

   Hi,

   i've never heard of autopkg before. Seems like an interesting project.

   What's are the requirements for an autopkg receipt?

   Regards, Mento

   • Edit

2. 2 Posted by davidcwest on 27 Jan, 2015 03:40 PM

   

   Actually I don't really know what I meant by that, I am new to trying to get packages working with AutoPkg and having a hard time working it out, I am not sure how you could make your installed autopkg friendly

   If you guys can there is info here https://github.com/autopkg/autopkg/wiki/Recipe-Format maybe it makes more sense to you than me :)

   • Edit

3. Support Staff 3 Posted by Luke Le on 13 Feb, 2015 06:00 PM

   

   Hi David,

   could you describe the exact problems you where seeing so we can better focus on where to start in adjusting our installer?

   That would be really helpful.

   • Edit

4. 4 Posted by davidcwest on 04 Mar, 2015 03:02 PM

   

   I can try, although not sure how much detail I can give, so sorry for my bad information.

   We use Casper Suite to distribute software and updates, (if you know Casper from JAMF sorry if this is condescending) it lets us put packages in a central location and then the jamf software on the clients OS X machine checks in, finds out if there are any policies to run, if there is one to install some software it grabs the pkg and installs it. Or something along those lines. The jamf software on the client is run as root.

   So I took the dmg from you guys, opened it, took the install.pkg and put that onto the Casper server then created a policy to install it. As far as I can tell it installs (in gpg pref it shows all up to date) but when I run Mail.app it still gives me the warning that the beta is out of date and all the gpg-ness of Mail.app is not there :)

   Sorry its probably not the details you want, if you can point me in the right direction I will try to gather whats needed.

   Thanks

   • Edit

5. Support Staff 5 Posted by Luke Le on 01 Apr, 2015 05:01 PM

   

   Hi David,

   it's possible that this already works now with beta 6. We've removed the beta limitation time.
   Could you try to test it again and let us know?

   Thanks!

   • Edit

6. 6 Posted by davidcwest on 07 Apr, 2015 11:42 AM

   

   Hello Luke,

   Just dropped the install.pkg into the casper system and pushed it out to a machine and it installs fine and shows up as the correct version and no more errors starting Mail.app :D

   Thanks

   • Edit

7. Steve closed this discussion on 07 Apr, 2015 12:53 PM.