May 2012 - Installer-dev - lists.apple.com

Re: Trying to import old .pkg bundles into flat distribution
by Stephane Sudre 21 May '12

21 May '12

AFAIK, you do not need to change your preflight and postflight scripts. - You just need to take into account that they are not called pre and post-installation scripts. - You can benefit from a new feature in flat packages that lets you attach a pre/post-installation script to a bundle. This removes the issue of having to figure out where the bundle gets actually installed by using the appropriate environment variable. BUT: - If you are using pre/post install or pre/post upgrade scripts in your bundle package, there's nothing like it in a flat package. And this requires changes. On Mon, May 21, 2012 at 4:42 PM, Mitchell Laurren-Ring <lists(a)rynosoft.com> wrote: > Bill: > > Can you be more specific about what changes are required for pre- and postflight scripts? > > /Mick > > > > > On May 16, 2012, at 12:00 PM, installer-dev-request(a)lists.apple.com wrote: > >> So yeah, you gotta flatten all your payloads, and if you have preflights and postflights, they'll require reworking. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Trying to import old .pkg bundles into flat distribution
by Mitchell Laurren-Ring 21 May '12

21 May '12

Bill: Can you be more specific about what changes are required for pre- and postflight scripts? /Mick On May 16, 2012, at 12:00 PM, installer-dev-request(a)lists.apple.com wrote: > So yeah, you gotta flatten all your payloads, and if you have preflights and postflights, they'll require reworking. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Codesigning apps in signed installers
by Edward Waxler 21 May '12

21 May '12

I've been able to verify Gatekeeper and our ability to sign our installers using our Developer ID Installer certificate. After going through that process, I noticed that once an installer is signed, the installed contents (i.e., applications) will run without issue, even though the executables themselves are not actually signed. I think we'll ultimately want to sign all of our executables with our Developer ID Application certificate regardless, but I'm just wondering - will it ever become strictly necessary to sign executables that are distributed via a signed installer? Or would it only be necessary to sign an app that's installed manually, e.g., by copying the bundle into /Applications? Thanks in advance, Ed _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Scripting additions to .plist?
by Fritz Anderson 18 May '12

18 May '12

If all you're asking is how to treat your users properly, you and your Windows counterpart are wise: Don't change users' settings out from under them. The usual way to deal with this is to ask to make the change upon the user's first launch of your installed software. — F On 2 May 2012, at 7:18 PM, Michele Corum wrote: > Really the question is not if we can add a line item to a .plist but "Do we > or do we not change user defined preferences?" > > My Windows counterpart here agrees with meuser defined is user defined and > we don't change those once a user has defined them. -- Fritz Anderson -- Xcode 4 Unleashed: Now in stores! -- <http://x4u.manoverboard.org/> _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Ehh, what's up Dock?
by Henri Shustak 18 May '12

18 May '12

You may be interested in the example deployment dock package (part of the additemtodock project : http://www.lucidsystems.tk/tools/additemtodock This is one approach which means you do not need to edit the "/System/Library/User Template". The way that package works is that it will overwrite the dock at login. However, you could modify it so that it simply ensures some specific applications are in the dock at login rather than managing the dock. I hope this information helps, even if it simply provides an alliterative avenue for you to explore. Note : If you use the example package, you may want to modify it to use LaunchD to kick off the scripts rather than Login Hooks. --------------------------------------------------------------------- This email is protected by LBackup, an open source backup solution. http://www.lbackup.org On 22/04/2012, at 3:51 PM, Paul Cook wrote: > > So, what if one also wants to add icons to the dock for yet to be created users? > > The templates for new users are stored in "/System/Library/User Template". Is there an easy way to also update each of these? > > Thanks for a really helpful and informative bit of information. > > Best Wishes, > > Paul > > On Mar 9, 2012, at 2:13 AM, Stephane Sudre wrote: > >>> 1) You have an issue in that you are updating the dock of the user whose home directory is denoted by "~" -- other logins will not be updated. Logins created later will not be updated. (In other emails, these issues have been discussed.) >> >> dockutil can do it for all existing user accounts, according to its >> documentation. > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Installer-dev mailing list (Installer-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/installer-dev/henri.shustak%40gmail… > > This email sent to henri.shustak(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Trying to import old .pkg bundles into flat distribution
by Bill Coderre 16 May '12

16 May '12

Short answer: Sorry, but yes. Signed flat distribution packages (aka mpkgs) can only contain flat payload packages. This is because the way we sign stuff only works for a single archive file (xar format), aka flat package. So yeah, you gotta flatten all your payloads, and if you have preflights and postflights, they'll require reworking. The good news is, your stuff will all be signed, and harder to damage in transit. On May 15, 2012, at 5:56 PM, Monte Benaresh wrote: > We currently use Iceberg to build .mpkg bundles from our .pkg bundles. However, it seems that in order to use Developer ID to sign our installer packages, we need to start using PM or Packages to create flat distributions that we can sign with productsign. > > So, we would like to be able to create new flat distribution projects which import our existing .pkg bundles. I tried this in PM, and it seems that once you include a .pkg, it will produce .mpkg bundles rather than flat distributions. As far as I can see, Packages cannot import .pkg bundles at all. > > Are my conclusions correct? In order to sign with Developer ID, will we be forced to re-create all of our package and metapackage projects with one of the newer tools? > > Thanks very much for any advice. > > Monte Benaresh > PACE Anti-Piracy > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Installer-dev mailing list (Installer-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/installer-dev/bc%40apple.com > > This email sent to bc(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Trying to import old .pkg bundles into flat distribution
by Monte Benaresh 16 May '12

16 May '12

Hello All, We currently use Iceberg to build .mpkg bundles from our .pkg bundles. However, it seems that in order to use Developer ID to sign our installer packages, we need to start using PM or Packages to create flat distributions that we can sign with productsign. So, we would like to be able to create new flat distribution projects which import our existing .pkg bundles. I tried this in PM, and it seems that once you include a .pkg, it will produce .mpkg bundles rather than flat distributions. As far as I can see, Packages cannot import .pkg bundles at all. Are my conclusions correct? In order to sign with Developer ID, will we be forced to re-create all of our package and metapackage projects with one of the newer tools? Thanks very much for any advice. Monte Benaresh PACE Anti-Piracy _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Problem in adding License files in Distribution Package
by Vikram Singh 12 May '12

12 May '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

setting a variable with the installer command?
by Allen Hancock 12 May '12

12 May '12

Hi all We have an installer which knows how to look inside the .pkg bundle for a variable which will be used during installation This, of course, rules out creating a flat / signed pkg Is there a way installer an pass a variable which a pre or post flight installation script could refer to? Otherwise, I'm sure I could simply "touch /tmp/some-file-name" or defaults write to a plist somewhere, and have the script read the variable we want to use. The nice part of having a switch in the installer command would be a 1 step solution, but I'm not sure that can work TIA for any ideas! -Allen _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: permissions (info)
by Don Montalvo 08 May '12

08 May '12

Apple should include a dialog box that says "Are you REALLY sure you want to change permissions on that file or folder?". Or better yet, PackageMaker should just plain not allow it...oh...wait...better yet...PackageMaker should trigger a 100,000 volt shock to the keyboard of anyone who decides to change permissions within PackageMaker. Wait...even mo' better...have the charge go to the person's chair...that ought'a provide a decent long term fix. Don Greg Neagle <greg.neagle(a)disneyanimation.com> wrote: > Of course you can. Set the correct owner, group and mode for all your files _before_ you add them to a PackageMaker project. > > PackageMaker is not a general file manipulation tool. > > -Greg _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0