Re: More - Safari Download Security Alerts
Re: More - Safari Download Security Alerts
- Subject: Re: More - Safari Download Security Alerts
- From: Dave <email@hidden>
- Date: Wed, 17 Dec 2008 18:18:34 +0000
On 17 Dec 2008, at 17:00, Jeremy Pereira wrote:
On 17 Dec 2008, at 15:27, Dave wrote:
On 17 Dec 2008, at 12:03, Jeremy Pereira wrote:
On 17 Dec 2008, at 11:28, Dave wrote:
Hi Mark,
Thanks a lot, it certainly is a lot easier to use and a lot less
flakey, but it still doesn't work. It does not create a folder
in "/Applications" it just installs the raw files there instead.
I'm giving up on PackageMaker, it just doesn't work and there
doesn't seem to be any support for it.
Seems crazy that you can't do this one simple thing with it, in
every other installer I've ever used this would have been a 5
min job, 2 days later using PackageMaker and still nothing. Oh
well, such is life.
It would be crazy if it were true, but it's not.
I've just created a simple package maker project that installs to
a sub directory of /Applications and it works absolutely fine.
Here's how I did it.
I created a directory in my home folder that mirrored the way I
want the final installation to look i.e.
/Users/jeremyp/
-> /Applications
-> /ASubDir
I put the distribution application in ASubDir, so I have this
directory structure:
/Users/jeremyp/
-> Applications/
-> ASubDir/
-> MyApp.app
In package maker, I added /Users/jeremyp/Applications as content.
On the right hand pane
Install was /Users/jeremyp/Applications
Destination was /Applications (I had to change this from "/")
After running the installer with the built package, I had a
subdirectory within /Applications called ASubDir containing my
application exactly as expected.
Please see my last post. Did you set the Destination on the
Contained and the Folder within it?
I'm not quite sure what you mean. It seems to me that what
actually happens is that PM takes everything *in* the folder you
specify in the Install field and copies it *into* the location in
the destination field.
I think the reason it's like this and the destination field
defaults to / is that a common use-case of PM is you want to
install lots of components in different places e.g. an application
in /Applications and a driver in /System/Library/Extensions.
In the lower section of the left hand pane in PM, when you drag the
folder to it, it creates a container, then inside that container
(click on the disclose triangle) it show the folder and the files in
it. It you click the container, it will show a Destination Field,
just setting this field alone does nothing AFAICT, if you then click
the folder it will show the contents pane, in here you have another
Destination field, if you leave that blank, the it defaults to "/". I
can't see the point of having the destination field in the content
item since you have to specify it for the folder anyway.
It doesn't seem to work unless you do this. To me this seems odd,
if left empty surely better behavior would be to use the
Containing Item's Destination rather than "/" ? If you wanted it
to go into "/", you could just override by entering "/" in the
folder Destination.
Also did you try it with files other than just the .app file? e.g.
the .app file and (say) a .txt file.
Yes. In fact, I just tried it with an empty directory in my
package and the empty directory was created successfully. I had
this structure:
$HOME/testpm/Applications/
subdir/
hosts (copied frome /etc/hosts)
emptydir/
I added $HOME/Applications as the content. The install field was
$HOME/Applications, the destination was /Applications
The subdir structure was created faithfully in /Applications
including the emptydir.
Incidentally, this method preserved the folder icon I set for the
subdir directory.
You are right it does install empty folders which is good. The
problem is that it doesn't install empty folders that are within
the .app bundle (I should have said this), e.g. I have an empty
folder: myApp.app/Contents/MacOS/Runtime/PlugIns (it just contains
a .ds_store file). This does not get created when the installer is
run. It's no big deal, just means that I will have to check if it
exists in my app and create it if not. I don't want to do this now,
since it will mean I'd have to re-submit the app to QA and we don't
have the time right now.
Whatever I try I cannot get it to create the custom Icon, again no
big deal.
Incidentally, I have now updated the AppleScript Installer to remove
the quarantine flags using xattr, this works well too.
So I can now ship both and let them decide which they want. I reckon
they will go for the AppleScript version, it's so much easier and
quicker. I just timed it, from opening the Script to the app
launching is about 10 seconds. By the time the user has opened the
package and clicked a few buttons, it's going to be about a minute
using PM I reckon, not a lot in it, but the AS version just flow
better IMO.
Thanks a lot all who have helped on this, I'm really grateful. I have
until tomorrow morning to get something working so all is now cool!
All the Best and Happy Holidays to All!
Dave
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden