September 2009 - Installer-dev

Re: How to include a distribution script flat package in another distribution script project?
by Iceberg-Dev 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=CKzoLGp9gpq44+sxiS9jXbBK4aLCMgn3xC6BlP9ZUWA=; b=Umb3A1tF+6rZYiiGxGkcgVwdsSFb/8OAnbtWem3FlJjJqKTotjlBcJ1LVaQTaaPyzx q1iu0E5qD8QKJysxXBJ77L0p70Y38++60sfx4LvWsyj5IlSqhtgDZXS2lX8oLbEmhAb5 JYNtRrQGU6hOaq8IeSq5My7M6W0xs2YrYEISk= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=Biw1DPm5pJsnrVQH8f2kZxehbwL/KItOKevaXLQp3lY7B2bNedOAh8lv98UZljHCbL y0mwHHLuazsiWDEVTqUXkG/PlZr1wpV4j23E7R6d8GoQicQ3o1Ehr8mUWh+sYHf/VdVw XtAZYqI3EGN+9+nP7lbDQm41mhOChyHA2PjQk= Hello, Is there something I am doing wrong or is this just outside the capability of distribution scripts? If the latter, then it seems that distribution scripts are less capable than metapackages to create installers where a large number of software components need to be gathered together. You need to merge the 2 distribution scripts into one. _______________________________________________ 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: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… On Sep 2, 2009, at 7:25 PM, Kennedy, Smith (Macintosh Software - IPG MCT) wrote: [...] my E.pmdoc, even though add C and D to the project, D comes up as a question mark. When I build E.pkg, it includes C but not D. You can not have a distribution script as a component of another distribution script. This email sent to site_archiver(a)lists.apple.com

1 0

How to specify name of my receipts?
by Brant Sears 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Any ideas? I've tried changing the choice name. Thanks. _______________________________________________ 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: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… I'm installing some things to various directories under /Library such as a LaunchAgent. The installer creates a receipt called "library.pkg". I'm trying to figure out where in PackageMaker I should specify the name of the receipt. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Never upgrade. Always install
by Carl Harris 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com I am running into an issue with my Installer where many times it will determine that the user should be upgrading their package rather than installing fresh. When this happens, files that are missing (usually the application bundle that should go to /Applications) is not installed. _______________________________________________ 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: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Justin Williams wrote: I have had very good luck with always having things properly installed (apart from the fresh install vs. upgrade install) by doing the following: 1. Use agvtool to manage the CFBundleVersion in the app (including any embedded frameworks, preference panes, etc). Bump the version number in everything that has changed whenever a new package is generated. 2. Bump the package version (if you're using a .pmdoc for a flat package) whenever a new package is generated. Apart from the sometimes unexpected results of the Allow Relocation flag on the package components, following this practice seems to make the Installer.app behave itself, installing/upgrading/replacing the installed components properly. One note of caution: Strangely, the .pmdoc caches the CFBundleVersion when you add content using the PackageMaker GUI. I haven't found any way to convince PackageMaker to refresh the CFBundleVersion in the .pmdoc using freshly-built artifacts with different version numbers, short of either (a) removing the package content from the .pmdoc and re-adding it or (b) passing the XML inside of the .pmdoc through an XSLT transform to "edit" the version attribute on each <component> element. This seriously complicates using the .pmdoc with a command- line build process, but failing to update version attributes on the components in the .pmdoc will virtually guarantee that the install will not be correct in many cases. In Leopard, I used to simply strip the version attribute from the component elements, but that doesn't work under Snow Leopard -- the Installer app isn't happy to find package components with no version number specified. I, too, find it very frustrating to work with PackageMaker's many faults. I love drag-and-drop install, but there are times when that just isn't feasible. Having to engage in a wrestling match with PackageMaker is a huge waste of time and increases my cost for developing on Mac OS X. Apple would do well to invest a *little* more effort in making it work better. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Never upgrade. Always install
by Jim Dodd 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1251918643; bh=RJ9YIRBftf7kHwrIxGPRypzUKMgbV3mxaWUkKKWLMMc=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=JwaTEyqt3+QPdLV2ijtkHu43p7Esvfy9YaCACG/FWFQ+u4Z+ghYX11BqHkcS3ivpcOc0+Kv+HYAkVYlYUf4hAASH7UGmppw/m+QKbzbUPC2iQ6QusfgGA47n329OSYYlpIzaEFcFvoVIQh5fMWCkUCblBKO8PXdYt4D3U+GQ4fw= Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=CLEKoREdK3OtOl38DJtN/+KCnSmCZwuowAKvJaoEAqIMDSSexuqKjmeTH4DmlTK1639YqPIxWIqYrLpz/rWqXVZBw+tEvMQ4MVQ8Gdkx+2TmiKozZSPyYFWqBlKER6o8YMiZVlu3hWHTSRWSGFmgYugkT/R2Mcqr8O7KIKuvHEY=; Also, if you are not creating a flat package but have a PKG file that you can look inside, look for a TokenDefinitions.plist in YourApp.pkg/Contents/Resources and open the TokenDefinitions.plist and drill down through pkmk-token-xx/Item x/searchPlugin to see what the Installer will be using as a search algorithm. You can set that to just look for your application in a specific place as we have done. Regards, Jim Dodd Onset Computer Corporation ----- Original Message ---- > From: Andrew Peckover <apeckover(a)pgmusic.com> > To: Justin Williams <justin(a)secondgearsoftware.com> > Cc: installer-dev(a)lists.apple.com > Sent: Wednesday, September 2, 2009 2:51:02 PM > Subject: Re: Never upgrade. Always install > > If Allow Relocation is enabled, then it looks for the .app on your computer, and > will put it elsewhere (not where you might expect) if it finds it. For example, > if you're testing your install on a computer that you use for development and > you've got the app in a few different places. A typical user wouldn't > experience this, since they would only have the .app in one place. > > But - note: If you uncheck the Allow Relocation box, you can't just forget > about this setting.... Because it often becomes automatically checked when you > modify your package.. > > Andrew > > ----- Original Message ----- From: "Justin Williams" > > To: "Andrew Peckover" > Cc: > Sent: Wednesday, September 02, 2009 11:07 AM > Subject: Re: Never upgrade. Always install > > > > Hi, > > > > The Allow Relocation checkbox is enabled, but in my testing, I'm not channging > the default setting of installing to /Applications. Would disabling the Allow > Relocation checkbox make a difference? > > > > - j > > > > > > On Sep 2, 2009, at 11:28 AM, Andrew Peckover wrote: > > > >> Hello Justin, > >> > >> > >> the application bundle that should go to /Applications) is not > >> installed.> > >> > >> Are you sure that this isn't being caused by that allow relocation checkbox > in the Components section? Just making sure. > >> > >> -- > >> I haven't found a way around the 'upgrade' issue either, other than to > always make sure when I change the contents of my package I use a different > folder name for my source files. Then at least customers' files don't get > deleted (which I still can't believe is allowed) > >> > >> Andrew > >> > >> > >> > >> ----- Original Message ----- From: "Justin Williams" > > >> > > >> To: > >> Sent: Wednesday, September 02, 2009 8:56 AM > >> Subject: Re: Never upgrade. Always install > >> > >> > >>> It's a metapackage that contains an application file and another subpackage > that installs some config files and certificates into the Library folder. We > build each package on the fly using a set of scripts, because the subpackage's > contents is unique to each user. Before I got around this issue by just > trashing the receipts files in / Library/Receipts/ but with the transition away > from those, I haven't found a reliable way to accomplish it in Leopard & Snow > Leopard. > >>> > >>> - j > >>> > >>> > >>> On Sep 2, 2009, at 10:53 AM, Nick Peelman wrote: > >>> > >>>> Howard brings up an interesting question...what else are you > >>>> installing that makes an installer necessary? I assume you're dumping > >>>> files into /Library or a Kext or something? > >>>> > >>>> -nick > >>>> > >>>> On Wed, Sep 2, 2009 at 10:33 AM, Justin > >>>> Williamswrote: > >>>>> Hi, > >>>>> > >>>>> I am running into an issue with my Installer where many times it will > >>>>> determine that the user should be upgrading their package rather than > >>>>> installing fresh. When this happens, files that are missing (usually the > >>>>> application bundle that should go to /Applications) is not installed. > >>>>> > >>>>> I'd prefer to set my package to never have the option to upgrade and to > just > >>>>> always install/overwrite the existing file on the user's Mac. I > thought I > >>>>> could do this by adding the "pkgutil --forget net.secondgear.mybinary" > >>>>> command to my postinstall script to remove it from the receipts database, > >>>>> but it doesn't seem to make a difference. > >>>>> > >>>>> What's the preferred method to handle something like this? I was hoping > >>>>> there would be a magic button I could click in PackageMaker, but sadly, it > >>>>> didn't seem to exist. > >>>>> > >>>>> Any help would be appreciated. > >>>>> > >>>>> - > >>>>> Justin Williams > >>>>> http://secondgearsoftware.com/ > >>>>> - > >>>>> Check out Today: snapshot view of your daily iCal agenda > >>>>> > >>>>> - > >>>>> _______________________________________________ > >>>>> 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: > >>>>> http://lists.apple.com/mailman/options/installer-dev/nick %40peelman.us > >>>>> > >>>>> This email sent to nick(a)peelman.us > >>>>> > >>>> > >>>> > >>>> > >>>> -- Nick Peelman > >>>> peelman(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: > >>> http://lists.apple.com/mailman/options/installer-dev/apeckover%40pgmusic.com > >>> > >>> This email sent to apeckover(a)pgmusic.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: > http://lists.apple.com/mailman/options/installer-dev/bcbuilderboy%40yahoo.c… > > This email sent to bcbuilderboy(a)yahoo.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: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

RE: [launchd-dev] launch_msg(): Socket is not connected
by Grant Erickson 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Organization: Nuovation System Designs, LLC Thread-index: Acor/7XJFhJ3DVHpoEKZw8jRSE73UQ== Thread-topic: [launchd-dev] launch_msg(): Socket is not connected User-agent: Microsoft-Entourage/12.20.0.090605 On Wed Jun 24 04:14:23 PDT 2009 Quinn <eskimo1(a)apple.com> wrote: > At 23:31 +0530 18/6/09, Arjun SM wrote: >> I will take your word for it . I was of the notion that i have to >> support multiple users for my application. > > Well, there's a difference between supporting multiple users and > supporting all of the edge cases brought about by multiple users. I > totally agree that you should support multiple GUI users in general. > However, that presents some unique install, upgrade and uninstall > problems, and I think it's better that you solve those problems in a > nice simple manner (forcing a restart in the multiple user case, for > example) than do some convoluted hack that will break in mysterious > ways in the future. > > But hey, Mac OS X is a very open platform so you get to choose how to > spend your development time. > > And yes, we do recognise that this is a nasty wrinkle in the whole > launchd story and we hope to fix this eventually. It would appear that I just ran into this same problem with my preflight and postflight scripts for my agent / preference pane package. I solved the installer-side issue of launchctl running with root/admin credentials as Arjun did by using sudo/su; however, from this thread, it sounds like the: launch_msg(): Socket is not connected is a fatal dead end for the {pre/post}flight approach. My scripts effectively amount to: preflight: if "${LaunchctlExecutable}" list | /usr/bin/grep "${LaunchctlLabelRegex}" 2>&1 > /dev/null; then sudo -u "${USER}" "${LaunchctlExecutable}" remove "${LaunchctlLabel}" fi postflight: if [ -r "${LaunchctlPath}" ]; then sudo -u "${USER}" "${LaunchctlExecutable}" load -S "${LaunchctlSession}" "${LaunchctlPath}" fi Has anyone had any luck setting KeepAlive to true in their job description and then using a kqueue in their agent to monitor either its Info.plist or the executable itself and then quit and let launchctl restart it when it detects a version change or unlink of said files? It seems like this would also address the multi-user case which, while rare, still needs to be solved and is NOT addressed with the {pre,post}flight approach. I realize, of course, that I can set the restart flag in the package; however, from a user experience perspective that's less than ideal and is not entirely compatible with Sparkle (as near as I can tell). Regards, Grant _______________________________________________ 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: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Never upgrade. Always install
by Andrew Peckover 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Andrew Hi, - j On Sep 2, 2009, at 11:28 AM, Andrew Peckover wrote: Hello Justin, <When this happens, files that are missing (usually the application bundle that should go to /Applications) is not installed.> Andrew - j On Sep 2, 2009, at 10:53 AM, Nick Peelman wrote: Howard brings up an interesting question...what else are you installing that makes an installer necessary? I assume you're dumping files into /Library or a Kext or something? -nick On Wed, Sep 2, 2009 at 10:33 AM, Justin Williams<justin(a)secondgearsoftware.com> wrote: Hi, Any help would be appreciated. This email sent to nick(a)peelman.us -- Nick Peelman peelman(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: http://lists.apple.com/mailman/options/installer-dev/apeckover%40pgmusic.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: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… If Allow Relocation is enabled, then it looks for the .app on your computer, and will put it elsewhere (not where you might expect) if it finds it. For example, if you're testing your install on a computer that you use for development and you've got the app in a few different places. A typical user wouldn't experience this, since they would only have the .app in one place. But - note: If you uncheck the Allow Relocation box, you can't just forget about this setting.... Because it often becomes automatically checked when you modify your package.. ----- Original Message ----- From: "Justin Williams" <justin(a)secondgearsoftware.com> To: "Andrew Peckover" <apeckover(a)pgmusic.com> Cc: <installer-dev(a)lists.apple.com> Sent: Wednesday, September 02, 2009 11:07 AM Subject: Re: Never upgrade. Always install The Allow Relocation checkbox is enabled, but in my testing, I'm not channging the default setting of installing to /Applications. Would disabling the Allow Relocation checkbox make a difference? Are you sure that this isn't being caused by that allow relocation checkbox in the Components section? Just making sure. -- I haven't found a way around the 'upgrade' issue either, other than to always make sure when I change the contents of my package I use a different folder name for my source files. Then at least customers' files don't get deleted (which I still can't believe is allowed) ----- Original Message ----- From: "Justin Williams" <justin(a)secondgearsoftware.com > To: <installer-dev(a)lists.apple.com> Sent: Wednesday, September 02, 2009 8:56 AM Subject: Re: Never upgrade. Always install It's a metapackage that contains an application file and another subpackage that installs some config files and certificates into the Library folder. We build each package on the fly using a set of scripts, because the subpackage's contents is unique to each user. Before I got around this issue by just trashing the receipts files in / Library/Receipts/ but with the transition away from those, I haven't found a reliable way to accomplish it in Leopard & Snow Leopard. I am running into an issue with my Installer where many times it will determine that the user should be upgrading their package rather than installing fresh. When this happens, files that are missing (usually the application bundle that should go to /Applications) is not installed. I'd prefer to set my package to never have the option to upgrade and to just always install/overwrite the existing file on the user's Mac. I thought I could do this by adding the "pkgutil --forget net.secondgear.mybinary" command to my postinstall script to remove it from the receipts database, but it doesn't seem to make a difference. What's the preferred method to handle something like this? I was hoping there would be a magic button I could click in PackageMaker, but sadly, it didn't seem to exist. - Justin Williams http://secondgearsoftware.com/ - Check out Today: snapshot view of your daily iCal agenda <http://secondgearsoftware.com/today/> - _______________________________________________ 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: http://lists.apple.com/mailman/options/installer-dev/nick %40peelman.us This email sent to apeckover(a)pgmusic.com This email sent to site_archiver(a)lists.apple.com

1 0

Snow Leopard installer scripts
by Jim Dodd 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1251916708; bh=q83N/+rGHKohLmt4f2mEsXq7Nnan4GaAm3K35aE8pfA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=GrE8XeeNZQlfWGhmM3OCHzlR7l+iAjB7JlreJLkCUpnKQjpisjhA+ZFwCQZgwa4MDU5ZKP95Nb8FD3jdsXxi7PcPGqmMIZ4X40RCVoug3Doa84cC6BzmJfUkCHVeB8kGEy6b+OMwUF0z7rPBRJxsSYPSJtkw1kYEXOcgTyZFdBo= Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=FhGCniEhwa7IuHfaMEQx9ULju4qCM6dNdMluwHNXTGllM84ENQtzdl9jUa+ICFX1Hh8d/FY9Ml+LjelO8yV/HCU/Ti1mPRQtrdQiQmsmrBu4+kusUOuG9bKQFj+qWtJ2gkhqIdMQNHm1ydaqHdgMq/kKPeuWmkTo7OJuFlSIh4k=; Under Snow Leopard, OS X 10.6, it appears that the number of arguments passed from the Installer.app to the pre- and post-install scripts is smaller than in previous versions of the Installer. Can anyone verify that the fourth argument, the root directory for the current System folder, is missing? The third parameter, the mountpoint of the destination volume, has always been the same from what I've seen so far but I could imagine that they would be different if you were installing to an external drive. Or is it the third parameter that is missing? Is there a way to get the root directory for the current System folder or should I just always assume this is "/" ? Or, if it is the third parameter that is missing, is there a way to get the mountpoint of the destination volume? Thanks for any help you can offer. Regards, Jim Dodd Onset Computer Corporation _______________________________________________ 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: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Never upgrade. Always install
by Justin Williams 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi, - j On Sep 2, 2009, at 11:28 AM, Andrew Peckover wrote: Hello Justin, <When this happens, files that are missing (usually the application bundle that should go to /Applications) is not installed.> Andrew - j On Sep 2, 2009, at 10:53 AM, Nick Peelman wrote: -nick On Wed, Sep 2, 2009 at 10:33 AM, Justin Williams<justin(a)secondgearsoftware.com> wrote: Hi, Any help would be appreciated. This email sent to nick(a)peelman.us -- Nick Peelman peelman(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: http://lists.apple.com/mailman/options/installer-dev/apeckover%40pgmusic.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: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… The Allow Relocation checkbox is enabled, but in my testing, I'm not channging the default setting of installing to /Applications. Would disabling the Allow Relocation checkbox make a difference? Are you sure that this isn't being caused by that allow relocation checkbox in the Components section? Just making sure. -- I haven't found a way around the 'upgrade' issue either, other than to always make sure when I change the contents of my package I use a different folder name for my source files. Then at least customers' files don't get deleted (which I still can't believe is allowed) ----- Original Message ----- From: "Justin Williams" <justin(a)secondgearsoftware.com > To: <installer-dev(a)lists.apple.com> Sent: Wednesday, September 02, 2009 8:56 AM Subject: Re: Never upgrade. Always install It's a metapackage that contains an application file and another subpackage that installs some config files and certificates into the Library folder. We build each package on the fly using a set of scripts, because the subpackage's contents is unique to each user. Before I got around this issue by just trashing the receipts files in / Library/Receipts/ but with the transition away from those, I haven't found a reliable way to accomplish it in Leopard & Snow Leopard. Howard brings up an interesting question...what else are you installing that makes an installer necessary? I assume you're dumping files into /Library or a Kext or something? I am running into an issue with my Installer where many times it will determine that the user should be upgrading their package rather than installing fresh. When this happens, files that are missing (usually the application bundle that should go to /Applications) is not installed. I'd prefer to set my package to never have the option to upgrade and to just always install/overwrite the existing file on the user's Mac. I thought I could do this by adding the "pkgutil --forget net.secondgear.mybinary" command to my postinstall script to remove it from the receipts database, but it doesn't seem to make a difference. What's the preferred method to handle something like this? I was hoping there would be a magic button I could click in PackageMaker, but sadly, it didn't seem to exist. - Justin Williams http://secondgearsoftware.com/ - Check out Today: snapshot view of your daily iCal agenda <http://secondgearsoftware.com/today/> - _______________________________________________ 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: http://lists.apple.com/mailman/options/installer-dev/nick %40peelman.us This email sent to apeckover(a)pgmusic.com This email sent to site_archiver(a)lists.apple.com

1 0

How to include a distribution script flat package in another distribution script project?
by Kennedy, Smith (Macintosh Software - IPG MCT) 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Acor8mYEfj5dxqdFTZOdl4QAVzXM1w== Thread-topic: How to include a distribution script flat package in another distribution script project? Hello, While I have made "old-school" packages and meta-packages in the past, I am somewhat new to the distribution script installers. I apologize if this is an elementary question, but I have had a lot of difficulty using or even understanding PackageMaker since 3.0 was released. In a number of cases we have stuck with PackageMaker 2.1.1, but in this context it seemed to make sense to roll to 3.0 and try to get it figured out. I was assuming that distribution scripts were able to wrap other "simple" packages or other distribution script packages, but the latter is giving me some problems. Here is my scenario: A.pkg is a simple package B.pkg is a simple package C.pkg is a simple package D.pkg is a distribution script that deploys A and B. E.pkg is a distribution script that deploys D and C. In my E.pmdoc, even though add C and D to the project, D comes up as a question mark. When I build E.pkg, it includes C but not D. Is there something I am doing wrong or is this just outside the capability of distribution scripts? If the latter, then it seems that distribution scripts are less capable than metapackages to create installers where a large number of software components need to be gathered together. Any help would be appreciated. Smith _______________________________________________ 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: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Never upgrade. Always install
by Andrew Peckover 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hello Justin, <When this happens, files that are missing (usually the application bundle that should go to /Applications) is not installed.> Andrew - j On Sep 2, 2009, at 10:53 AM, Nick Peelman wrote: Howard brings up an interesting question...what else are you installing that makes an installer necessary? I assume you're dumping files into /Library or a Kext or something? -nick On Wed, Sep 2, 2009 at 10:33 AM, Justin Williams<justin(a)secondgearsoftware.com> wrote: Hi, Any help would be appreciated. - Justin Williams http://secondgearsoftware.com/ - Check out Today: snapshot view of your daily iCal agenda <http://secondgearsoftware.com/today/> - _______________________________________________ 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: http://lists.apple.com/mailman/options/installer-dev/nick %40peelman.us This email sent to nick(a)peelman.us -- Nick Peelman peelman(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: http://lists.apple.com/mailman/options/installer-dev/apeckover%40pgmusic.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: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Are you sure that this isn't being caused by that allow relocation checkbox in the Components section? Just making sure. -- I haven't found a way around the 'upgrade' issue either, other than to always make sure when I change the contents of my package I use a different folder name for my source files. Then at least customers' files don't get deleted (which I still can't believe is allowed) ----- Original Message ----- From: "Justin Williams" <justin(a)secondgearsoftware.com> To: <installer-dev(a)lists.apple.com> Sent: Wednesday, September 02, 2009 8:56 AM Subject: Re: Never upgrade. Always install It's a metapackage that contains an application file and another subpackage that installs some config files and certificates into the Library folder. We build each package on the fly using a set of scripts, because the subpackage's contents is unique to each user. Before I got around this issue by just trashing the receipts files in / Library/Receipts/ but with the transition away from those, I haven't found a reliable way to accomplish it in Leopard & Snow Leopard. I am running into an issue with my Installer where many times it will determine that the user should be upgrading their package rather than installing fresh. When this happens, files that are missing (usually the application bundle that should go to /Applications) is not installed. I'd prefer to set my package to never have the option to upgrade and to just always install/overwrite the existing file on the user's Mac. I thought I could do this by adding the "pkgutil --forget net.secondgear.mybinary" command to my postinstall script to remove it from the receipts database, but it doesn't seem to make a difference. What's the preferred method to handle something like this? I was hoping there would be a magic button I could click in PackageMaker, but sadly, it didn't seem to exist. This email sent to apeckover(a)pgmusic.com This email sent to site_archiver(a)lists.apple.com

1 0