packagemaker

I want to do my installation of pkg file as silent install from mac terminal. So i used the below command to do silent install. sudo installer -store -pkg "/User/MyName/Desktop/helloWorld.pkg" -target / It perfectly installed my application. But i want to pass arguments from this command line script to package installer that was created in package maker. So that i can able to use this argument value in post/pre installation script inside the package installer. Is there any possibility to pass my value as argument in the above command? This is not possible from the command since the " installer

My installer is created using PackageMaker. After that I codesigned the installer using the following command. productsign --sign 'Blah, Inc.' Install.mpkg/ CS/Install.mpkg This seem to work pretty well and I could see that it is signed using the following command. pkgutil --check-signature Install.mpkg Since the certificate is installed on my system in keychain, the installer seem to show a little lock on top right corner. Clicking this opens up the certificate. If the installer is placed in a system without the certificate installed the lock is no longer seen. However I could still run the

I am using PackageMaker for the installer of my application (which is more than a simple bundle). I am wondering how to create an uninstaller, where to install it and how to provide to the user a way to launch it. Thanks in advance for your help, While implementing an uninstaller for some MAC OS application, we've come up with an idea. As SerpicoLugNut says: Seriously - 98% of Mac apps don't offer an uninstaller, and if most people want the app uninstalled, they will just drag the app to the trash We deviced that we can watch the Trash, and in case our application appears in the Trash, we can

I'm running a business where we are creating email stationeries for people. We have some Mac users that currently have to download a zip file and manually copy that to their mail stationeries directory. I want to automate that process and allow Mac users to download directly a package that will copy those files automatically. I've build a sample package with PackageMaker, created script that will replace Archive.pax.gz with client's stationeries but go an error. I have realized I did not provide a mandatory BOM file. How can I create it on a non-mac platform? Or if I can't, is there any other

There is a command to ease the pain of managing packages for Android phone, adb shell pm uninstall org.kde.necessitas.example.one adb shell pm uninstall org.kde.necessitas.example.two But I have many phones and just want to delete all packages from a particular domain on them. It cannot be done by adb shell pm uninstall org.kde.necessitas.example.* what is your suggestion? You can use the following in a batch file: (I am assuming Windows though) adb shell pm list packages org.kde.necessitas.example > packages.txt for /F "tokens=2 delims=:" %%a in (packages.txt) do adb shell pm uninstall %%a

We need to build Mac packages on the fly and it would be convenient if there is a way to create the same on Windows or Linux platform instead of using PackageMaker on Mac. Any ideas? Nope, you can't. You could do a scripted ssh login and fire it off using osascript so you can automate the whole build from somewhere else, but you can only build for a Mac on a Mac. You could do all the builds on a Mac, though. It's much easier that way around. jcoffland I don't agree that this is impossible. You could certainly do all the things PackageMaker does on OSX on another OS. It's just a matter of

I need a way to add an application to the Login Items from a postflight script which is run as part of my installer. It needs to work on 10.5+. Preferably, it would work in a bash script. My application already requires administrative rights. The approach I found here: Mac OS Login Items with Arguments? seemed to be on the right track (included below)... but didn't work when I tried it on command line and I'm not sure how to make it install for All Users or if I need to add logic to check if it's already added to startup items before calling this code. #!/bin/bash /usr/bin/osascript -e "tell