• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Fed up with PackageMaker, any advice?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fed up with PackageMaker, any advice?


  • Subject: Re: Fed up with PackageMaker, any advice?
  • From: Sidney San Martín <email@hidden>
  • Date: Tue, 13 Oct 2009 11:12:53 -0400

On Fri, Oct 9, 2009 at 12:35 PM, Kevin Brock <email@hidden> wrote:
> It's possible to create a script-only target.  Put one as the first
> component, and one as the last.  It's a hack, and you'll see that target in
> the GUI when the scripts are run, but it works.  I really wish they'd either
> kept the global pre- and post- or let us define our own actions to extend
> what's possible in the actions pane.

Thanks, Kevin. I'm not seeing this option in the PackageMaker UI, and
if I create a component but leave its contents empty, PackageMaker
spits out a warning and doesn't include it in the built package. Am I
missing something?

> Can't say much about raw editing mode.  Haven't used that much.  Since I
> only need to install on 10.5+ for most of my packages I've been using flat
> packages, and they're structured very differently from bundle packages.
>  They also don't support plugins, so they wouldn't work for you...
> I've been pretty happy with the XML files, because they make it easy to
> write build scripts that manipulate the PM generated files after the fact to
> make needed changes.  For example, there's a bug WRT versions that you need
> to work around by modifying the files by hand if you're doing automated
> command line builds.  It only affects bundles that are being installed, so
> it doesn't sound like you need to worry about it...

It looks like I can include everything (except the plugin) with the
scripts directory path, so I may be able to avoid the problems with
raw editing. If I can get a good, working pmdoc put together in
PackageMaker, modifying it at build-time probably works.

> From your description it sounds like what you need is possible under PM
> without much customization beyond the plugin you already have.  Your level
> of comfort with the XML files is an important factor if you need to tweak
> things after the fact though.
> There are a number of people on this list using Iceberg, a freeware
> installation package builder, but I don't know much about it myself.  It's
> at
> http://s.sudre.free.fr/Software/Iceberg.html
> if you want to take a look.

I tried Iceberg... I like it a lot, it's much more straightforward
than PM and let me put together a working package in no time. Even if,
for whatever reason, I go back to PackageMaker (I can't find a way to
script Iceberg, for instance), using Iceberg let me get unstuck making
a package so I move on to finishing my scripts and plugin. Thanks
again.
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Fed up with PackageMaker, any advice?
      • From: Kevin Brock <email@hidden>
References: 
 >Fed up with PackageMaker, any advice? (From: Sidney San Martín <email@hidden>)
 >Re: Fed up with PackageMaker, any advice? (From: Kevin Brock <email@hidden>)

  • Prev by Date: Re: Conditionally build different versions of a package?
  • Next by Date: Re: Fed up with PackageMaker, any advice?
  • Previous by thread: Re: Fed up with PackageMaker, any advice?
  • Next by thread: Re: Fed up with PackageMaker, any advice?
  • Index(es):
    • Date
    • Thread