Re: [MACTCL] OS X tcl/tk installation

[Jim I. <ji...@ap...>]

Sean,

I agree, packages are definitely the way to go.  I haven't played around
with PackageMaker yet, but it does look pretty straightforward.  One really
convenient way to set this up would be to add a shell script build phase to
the Tk makefile that takes the Tcl & Tk frameworks, and the Wish App that
have just been built, and makes up a package out of them.  Even though Tcl
is a separate project, I think it is okay to assume it is built the same
buildroot as Tk, since otherwise the debugger won't work, etc...

We could have the shell script only trigger when some environment variable
is set, and set that only in the Development build style.  The other way to
do this is to do it on install only, but that means you have to run
pbxbuild, right now, which is kind of hacky...  This is a known PB bug,
BTW...

This would be quite convenient.  If you already know how to do this, and are
interested, I would happily take a patch or two :-)  Otherwise, I will get
to it sometime - but probably later...

Jim

> 
> 
> The basics of getting a .pkg set up is quite simple and I'd highly
> recommend it.  You can easily set up the installation script that was
> given to be auto-executed on installation.  I'll see if I can find my
> notes on the subject, but it goes something like this:
> 
> 1) Create a README* file (* can be txt, rtf, rtfd, etc)
> 2) Create a LICENSE* file
> 3) Put the readme, license, and optional install scripts into a directory
> by themselves (This is the Resource directory)
> 4) Create an install tree that has what you want where you want it to go
> (This is the PackageRoot -- this may be empty, though not recommended)
> 5) Run PackageMaker (in the devTools) and point the PackageRoot and
> Resource directory to where they need to be, and build the package
> 
> There is a checkmark for whether admin access is required and whether
> there to require affirmation of the license, among a few other options.
> 
> Once done, PackageMaker will automagically generate the .pkg installer for
> you.
> 
> Throw that .pkg into a read-only .dmg with the readme and you are set to
> deliver a thoughtless/full install.
> 
> As a side note, as I mentioned, you don't have to give the PackageRoot.
> The tar.gz could be a resource that is installed by a hook script.  There
> are four scripts that are optionally run, if they exist, on upgrade and/or
> install.  You can have a script that runs before installation, and one
> that runs after.
> 
> Like I said, I'll see if I can get my notes on this.  It really is pretty
> simple, and elegant, but a concrete example would get the idea across much
> better. 
> 
> Cheers!
> 
> Sean
> 

-- 
++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=
Jim Ingham                              ji...@ap...
Developer Tools - gdb