Menu
▾
▴
Re: [Visualpython-users] Mac help?
|
From: Steve S. <st...@sp...> - 2010-03-30 10:42:01
|
Also.. I see there is a command line version of the installer tool with a "verbose" option. It might give some clues: vh10-96:~ steve$ /usr/sbin/installer -help Usage: installer [options...] -pkg <pathToPackage> -target <device> Options: [-dominfo] # Display domains that can be installed into. [-volinfo] # Display volumes that can be installed onto. [-pkginfo] # Display package that will be installed (for metapackages, shows contents). [-query] <flag> # Display information about package metadata. [-allow] # Allow installing an older version of a package over a newer one (for package versioning). [-dumplog] # Write log information to standard error (in addition to the usual syslog). [-help] # Display this help information. [-verbose] # Display detailed information. [-verboseR] # Display detailed information with simplified progress output. [-vers] # Display this tool version. [-config] # Display command line parameters in XML plist format. [-plist] # Display -dominfo, -volinfo, or -pkginfo in XML plist format (ignored when performing installation). [-file <pathToFile>] # Configuration file supplying parameters in XML plist format. [-lang <ISOLanguageCode>] # Sets the default language Mac OS X will use after installation. [-listiso] # Lists the ISO language codes that are recognized. [-showChoicesXML] # Output XML data describing the choices and their properties and state. [-showChoicesAfterApplyingChangesXML <pathToFile>] # Apply changes specified in the file to the choices in the package and output the resulting XML data. See below for the file format description. [-applyChoiceChangesXML <pathToFile>] # Apply changes specified in the file to the package and proceeds with installation. See below for the file format description. Device: The -target <device> parameter is any one of the following: (1) One of the domains returned by -dominfo. (2) Device node entry. Any entry of the form of /dev/disk*. ex: /dev/disk2 (3) The disk identifier. Any entry of the form of disk*. ex: disk1s9 (4) Volume mount point. Any entry of the form of /Volumes/Mountpoint. ex: /Volumes/Untitled (5) Volume UUID. ex: 376C4046-083E-334F-AF08-62FAFBC4E352 Flags: RestartAction # Can optionally return one of the following: None RecommendRestart RequireLogout RequireRestart RequireShutdown Choices file-format: An XML file that is an array of choiceIdentifiers (as strings) to toggle. Each choiceIdentifier specified will be toggled in order -- exactly as if a user had clicked on its checkbox in Installer.app's customization pane. Examples: installer -pkg InstallMe.pkg -target CurrentUserHomeDirectory installer -pkg InstallMe.pkg -target '/Volumes/Macintosh HD2' -lang ja installer -volinfo -pkg InstallMe.pkg installer -pkginfo -pkg InstallMe.pkg installer -query RestartAction -pkg InstallMe.pkg installer -pkg InstallMe.pkg -target / -showChoices vh10-96:~ steve$ On Mar 30, 2010, at 6:25 AM, Steve Spicklemire wrote: > Hi Bruce, > > I'm not sure why Package Manager is having trouble with your > filenames/directories.. I'll try to see if I can figure that out, > however I do know it's possible to have PackageManager run scripts > after the files are extracted. Maybe a little python script could > just "fix things up" afterwards. I'll try to look into that as well. > > -steve > > On Mar 29, 2010, at 9:23 PM, Bruce Sherwood wrote: > >> I'm not working from a command line; I have no experience with >> that. I'm >> using PackageMaker. So I don't know how to answer your questions. >> >> Bruce Sherwood >> >> On 3/29/2010 8:43 PM, Nick Frisina wrote: >>> Two ideas come to mind quickly (I'll have more time in May) >>> >>> 1) does the file location perhaps get set when the archive is >>> created, >>> rather than when the archive is extracted? >>> perhaps use a -v (verbose) to see what is created ... >>> >>> 2) short term, create a symbolic link to the "correct named file" >>> as part of >>> the package distribution !? >>> >>> perhaps post the command string you are using. >>> >>> ciao >>> nickf >>> >>> On 30/03/2010, at 10:04 AM, Bruce Sherwood wrote: >>> >>> >>>> I hope someone with Mac experience can help me. I've prepared an >>>> installer for a significant update VPython 5.3 but am unable to >>>> make an >>>> installer for the Mac. >>>> >>>> Thanks to Kadir Haldenbilen, VPython 5.3 provides extrudable 3D >>>> text of >>>> any True Type font, which is very cool. This requires some extra >>>> modules >>>> beyond numpy, and these should be included in the installer for >>>> ease of >>>> use. Each of these modules has a folder of .py files plus an egg- >>>> info >>>> file that needs to be at the same level as the folder. In >>>> PackageMaker I >>>> list the egg-info files as usual, but alas PackageMaker creates an >>>> installer which when run places these egg-info files inside >>>> folders with >>>> the same name as the egg-info file, minus the ".egg-info" >>>> extension. >>>> This doesn't cause problems with numpy, but with one of the other >>>> modules it causes Python to fail to find modules inside the >>>> module folder. >>>> >>>> I of course Googled a bit without finding any information on >>>> this. It's >>>> frustrating that in PackageMaker I give a destination like >>>> .....site-packages/xxx.egg-info but it goes into >>>> .....site-packages/xxx/xxx.egg-info. Experimentally, if I move the >>>> egg-info file up one level, VPython 5.3 works fine. I cannot find >>>> any >>>> switches in PackageMaker to prevent this bizarre behavior. I also >>>> tried >>>> chmod-ing the egg-info files to match the permissions on the numpy >>>> egg-info file, but that didn't help. >>>> >>>> AAARRRGGGHHH!!! HELLLLLLLP! >>>> >>>> Bruce Sherwood >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Download Intel® Parallel Studio Eval >>>> Try the new software tools for yourself. Speed compiling, find bugs >>>> proactively, and fine-tune applications for parallel performance. >>>> See why Intel Parallel Studio got high marks during beta. >>>> http://p.sf.net/sfu/intel-sw-dev >>>> _______________________________________________ >>>> Visualpython-users mailing list >>>> Vis...@li... >>>> https://lists.sourceforge.net/lists/listinfo/visualpython-users >>>> >>> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Visualpython-users mailing list >> Vis...@li... >> https://lists.sourceforge.net/lists/listinfo/visualpython-users |
