Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Fri Jul 16, 2004 10:06 pm Post subject: /usr/bin/package doesn't exist on 10.3?
Quick query...I reached the end of my build, and lo! /usr/bin/package doesn't seem to exist on 10.3 systems. I think that PackageMaker itself may be the replacement for the old command line utility. I'm researching now to see what I need to do to fix the makefiles for Panther builds.
FWIW all of my Jag builds have been spotless Patrick, IIRC, doesn't build on 10.3, so I guess I'm one of the first
but I can't find what the command line args are for package in order to do the translation between old and new. Once I can figure those out it should be as simple as adding a unmae switch into the makefile to do one or the other (unless I'm mistaken)
but I can't find what the command line args are for package in order to do the translation between old and new. Once I can figure those out it should be as simple as adding a unmae switch into the makefile to do one or the other (unless I'm mistaken)
ed
I haven't used the command line version of PackageMaker in any version of Mac OS X, and I tried the obvious "/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker -help" in Mac OS X 10.3.x, except I got it wrong by using "--help", and it gave me no info (I shut my machine down after that, and didn't want to fire it up again to do it right) .
Apparently in Mac OS X 10.2.x, if you just type "package" it will give you help.
Here is a useful page on Mac OS X Installer/PackageMaker information, from the maker of Iceberg :
/usr/bin/package is, fortunately, a simple shell script that uses (hopefully) commonly-available shell commands like "mkdir", "pax", etc.
For now, you may just want to copy the script over from your Jaguar build. Then, while you are doing that, I can put the stripped down commands in the /usr/bin/package script into the NeoJ makefile.
I just checked in changes to the NeoJ makefile that does the same steps as the /usr/bin/package command does.
Can you cvs update your workspace and run "make" to see if it works?
BTW, you may also want to rebuild (in a separate terminal, of course) the vcl and setup2 modules after you cvs update but before you run "make" just to be sure that you have my latest setup script and SalLayout changes.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum