[jasonpgignac]

I’ve noticed this behaviour on occaision, but not very often. Here’s what I’ve noticed:

1) If you put an application .app file in a pkg, the system assumes /Applications. This path will usually not disappear on open/close.
2) If you path to your source files relative instead of absolute, the destination path seems to be more resilient. Weird, I know.
3) If you build at least once before saving, the destination path seems to be resilient. Again, weird I know.

It’s not like I build a thousand packages a week, so it’s possible that some of this is just anecdotal, but I figure others who are doing this can confirm or deny my observations.

[jasonpgignac]

We have had this issue in the past, but not with this panel – we had it when AD bound users tried to add Login Items under the Accounts panel – and usually it would freeze up and become altogether non-responsive. Does it happen with all kinds of users, local and directory? Did you set any keyboard/mouse prefs in your image that may be incorrect?

[jasonpgignac]

That’s how I’ve built all mine – it’s SO much easier too…

[jasonpgignac]

I don’t build our packages with InstaDMG directly, but the process has many parallels, and I can attest, the clearReg.pkg works like a charm. If you look in the guts of it, it’s actually remarkably simple – Apple won’t run the screens if there are a couple empty files sittin’ on the system, more or less. Gotta love sweet simplicity. As a side note (since this is how we use it) this also works GREAT as a bundled pkg in a NetInstall image made from the OS installer.

[jasonpgignac]

Hear, hear! I can confirm that. I just finished the book, after getting the book on preorder from Amazon. Server Essentials was a bit more tepid, but I can understand that it has to be geared real slow considering the topic, so I am willing to give it the benefit of the doubt. I have the other two ACSA books on order, and hope for the best!

[jasonpgignac]

We have to keep using the $%@# program, solely because it supports Stamp annotations. But then, most of my Mac users have Acro Pro installed, so, it’s more a PC issue for us.

[jasonpgignac]

I’m lazy, so my personal mantra is to modularize – and NEVER mix data with presentation as it were. The software itself is it’s own install, so that it is completely generic, and non-specific. This way if my company gets bought, for instance, I don’t have to rebuild a big package. Settings go in a seperate package – and as a general rule, even here I install individual settings in individual packages, so that, for instance, you might put bookmarks in their own package browser setting configurations in another, etc – again, so that if I have to change any specific setting, I can with a minimum of work. This is just like InstaDMG to me – the more you split it up, the more easily you can change it later. IF you know you’re going to install Firefox, plus the bookmarks, plus the browser configs over and over and don’t want to have to do three packages? That’s what mpkgs are for. B ut that’s just my opinion, YMMV.
.

[jasonpgignac]

Perhaps I’m missing something, but I still don’t understand why you can’t just make it a launchDaemon. What’s up with the computer naming script that it won’t work as a daemon?
And, if you’re happy with running the other scripts on user login, why not just make them a login hook for whatever account gets logged in the first time the computer is booted up? Then you won’t have to deal with those permissions issues on the last step

[jasonpgignac]

I got it – the PC was defaulting to TLS, had to switch to SSL. My bad! Thanks so much :).

[Author]

Posts