Apple

Thank you very much for your reply.

Yes, I want to check the mod dates of a lot of files, mainly to prevent accidentally downgrade.

Because it is not inside my app, so I may have to use script. But I think it’s hard for a pre/post-install script to check hundreds of file during the installation. I mean you can find which one is newer when installing, but you may not want to set hundreds of check scripts for every files in the package when you make the package.

To compare the installer’s version is my plan B. But I found the package won’t copy itself into the /Library/Receipts, it’s quite different from old versions of PM. (I use 3.0.2)

And I found that the installer won’t compare the “Package Version”, it just directly replace even if I build an old version.

Are these two phenomenon bugs, or there is some configuration should be set?

Best Regards,

Kevin Gu

From: Gignac, Jason (HAS-SAT) [mailto:email@hidden]
Sent: 2008年9月26日 10:53
To: Gu, Kevin; email@hidden
Subject: Re: Migration from VISE to PackageMaker

I'm no expert, like some of these folks, but I can answer your first question - no. The point (arguably a valid one) of this is that packages install the application's static resources. I am assuming that if you want to check mod dates of a file, it is because you don't want to overwrite something the user has configured, or accidentally downgrade a shared library or something. Apple would, then offer two options.
If you are trying to deal with setting up basic configuration if the app has not been configured, Apple would probably argue that this is something best done by the app itself. Many apps will heal themselves conf wise if there is no conf or damaged conf when they startup. There is also the added advantage that this repairs in case of damage to vola(ile files.

If it is a shared lib or something, that is when you would use a postscript to test if the file is newer then copy it

From: installer-dev-bounces+jason.gignac=email@hidden
To: email@hidden
Sent: Thu Sep 25 21:38:33 2008
Subject: RE: Migration from VISE to PackageMaker

Hi all,

Well, I have found the answer to the second question: Italiano is it; Nederlands is nl …

But I still don’t have any clue on the 1^st and 3^rd topic.

Best Regards,

Kevin Gu

From: installer-dev-bounces+kevin.gu=email@hidden [mailto:installer-dev-bounces+kevin.gu=email@hidden] On Behalf Of Gu, Kevin
Sent: 2008年9月25日 17:02
To: email@hidden
Subject: Migration from VISE to PackageMaker

Hi all,

I used to make installers with VISE X, but now I plan to use Package Maker to make installers.

But I cannot find some important corresponding features in Package Make.

I’d be deeply appreciated for any kind of help on the following topics.

1) The replacement during installation. It seems that PM replaces files with same name unconditionally.

Is it possible to do the replacement only when the files are newer according to Creation date or Modification Date?

And, coz there are hundreds of files, is it possible to set the replacement condition separately? (Some by Date, some by Bundle version, some always replace)

2) The multi-language support. I found there are only five languages listed in the “Add Localization” list, can I add other languages such as Italiano and Nederlands so that the installer will launched in such language when user set such language as default language in “International” in “System Preferences”?

Is there any languages supported by PM but not listed?

3) I found that the PM project cannot remember the destination in “Configuration” of “Contents”. Neither can it remember the permissions (Owner, Group, Mode: rwxrwx…) of the files.

Are these bugs? Or am I set something wrong?

Thanks in advance.

Kevin

References:
	>Re: Migration from VISE to PackageMaker (From: "Gignac, Jason (HAS-SAT)" <email@hidden>)