Tim Jenness wrote:
> JAC do not want to be the next people to make an OSX Starlink release.
> Next time it's Starlink's job... :-)
The actual process of making the release is really simple:
- set the user:group of all files in the tree to root:wheel (this might not
actually be necessary if you don't ask for authorization in the appropriate
PackageMaker location... see
http://developer.apple.com/documentation/DeveloperTools/Conceptual/SoftwareDistribution/Concepts/sd_permissions_author.html
or http://tinyurl.com/46cvm for further discussion on file ownership w.r.t.
Packages)
- run up PackageMaker
- load the Starlink PackageMaker project
(http://www.jach.hawaii.edu/~bradc/starlink/star-pack.tar.gz)
- change relevant bits, especially the directory located under the Resources
tag -- this should be set to whereever you unpacked the above file -- and the
root directory under the Files tag.
- File > Create Project, save into an empty directory
- run up Disk Utility
- Images > New > Image from Folder..., create an image from the directory
you saved the project in
- put disk image somewhere downloadable.
That whole process takes maybe an hour, and 90% of that time is spent waiting
for PackageMaker to create the package and Disk Utility to create the disk
image. Once you have everything set up the first time, subsequent times are
pieces of cake.
Depending on one's mood, one could even create a script that would
automatically add the "source /local-star/etc/[login|cshrc]" lines to the
user's [.login|.cshrc] files, but I decided not to do that for this release
(see
http://developer.apple.com/documentation/DeveloperTools/Conceptual/SoftwareDistribution/Concepts/sd_pre_post_processing.html
or http://tinyurl.com/3w37u)
There's more information available at Apple's website:
http://developer.apple.com/documentation/DeveloperTools/Conceptual/SoftwareDistribution/index.html
or http://tinyurl.com/6xwgv
And Apple needs shorter URLs on their Developer Connection website.
Cheers,
Brad.
|