Installer built with PackageMaker only sometimes shows destination select screen - osx-lion

I have built a simple installer with PackageMaker 3.0.5. It installs a package into /Applications and some support files into /Library.
The distribution is set to easy install only, System volume only. Allow custom location is disabled for all of the contents. The app is set to allow downgrade and not allow relocation.
The installer does install correctly, but sometimes when I run the installer it displays a 'Select a Destination' screen and has a 'Change Install Location...' button, and sometimes it skips straight through to the 'Installation Type' screen.
I would prefer the second behaviour, but could live with either. My concern is the unexplained change in behaviour betweens runs. Does anyone know what causes this, and how to stop it?

As far as I've been able to determine, it has to do with the version of OS X where the installer is being run.
I built my installer using PackageMaker 3.0.3 on Mac OS X 10.5 and I have all the same settings you do.
When installing on OS X 10.5 I do not get the Destination Select pane, or the "Change Install Location..." button. But on 10.6 and 10.7 I see both.
I also have a custom install pane, which may changes things.
Sorry this isn't a real answer but I hope it helps.

I have the same problem on OS X Yosemite. Sometimes "destination select" shows up and sometimes not. Usually on the first time it shows up, but on consecutive runs it does not.

Related

What is VSCode User Setup for Windows?

On a Windows workstation after a recent update of VSCode I'm prompted (recommended) to install a "User Setup Distribution of VSCode for Windows"
The link for more info leads to:
Download User Setup
If you are a current user of the system-wide Windows setup, you will be prompted to switch to the user setup, which we recommend using from now on. Don't worry, all your settings and extensions will be kept during the transition.
I don't see anything that explains what changes this distribution makes or how it's different from a distribution for other platforms, like X11/linux.
Code is a great editor, so I use it on various platforms depending where I am. Where is the explanation of what is included in this updated "Distribution"?
https://code.visualstudio.com/updates/v1_26#_user-setup-for-windows
Famous Question Badge Celebration! : love to VSCodium https://vscodium.com/ ... and highly recommend to anyone interested in this Q.
VSCode User Setup is a new installer, with a new install strategy, which installs the whole executable for VSCode and its dependencies in directories which don't require system-level / administrator permissions to modify. This allows a few things:
Users who don't have admin privileges to their workstation can still install and use VS Code
VS Code can perform its updates with fewer prompts (basically without the system-level privilege escalation prompts)
One tip: If you already had VSCode installed as a system-wide installation and you switch to the new installer as prompted/recommended, the User Setup installer will suggest that you uninstall the system-wide install first. I was a little nervous that I might lose my extensions doing this, but I went ahead and tried it and am happy to report that my extensions, recent projects, and other data regarding my VSCode use remained intact between uninstalling the "old" version and then proceeding with install of the new User Setup version.
(I'm a first time responder after many years.)
Note there is another useful discussion on this subject at: (What is the migration procedure for moving from Windows system-wide Visual Studio Code to user setup?). I too got worried when I got unexpected messages from the install informing me that the version was already installed and asking me if I wanted to continue? I clicked NO, why continue if it is already installed. However, in the process I became aware of the distinction between 'distribution' and 'version'. It turns out that the install works pretty much flawlessly no matter how you go about it. You can delete the system-wide distribution or not. If you do delete, you can delete before the new install, (which I did). You can also delete after the new install. (I didn't read too closely but there might be an extra step if you want to use both distributions.) In hindsight, since all approaches work nearly flawlessly, a minimal amount of instruction is all that was required. But in foresight, a little extra information on what to expect would have expedited the process for several people, including me. P.S. I found the answers in this thread useful. Thanks.
From the page you link to:
This setup does not require Administrator privileges to install. It also provides a smoother background update experience.

Difference between User and System Installer of Visual Studio Code

Visual Studio code offers User and System Installer but I have not found any description about the differences between these two options.
Could someone please shed a light on this for me?
User setup for Windows
Announced last release, the user setup package for Windows is now available on stable. Installing the user setup does not require Administrator privileges as the location will be under your user Local AppData (LOCALAPPDATA) folder. User setup also provides a smoother background update experience.
Download User Setup
If you are a current user of the system-wide Windows setup, you will be prompted to install user setup, which we recommend using from now on. Don't worry, all your settings and extensions will be kept during the transition. During installation, you will also be prompted to uninstall the system-wide setup.
Reference: https://code.visualstudio.com/updates/v1_26#_user-setup-for-windows
I installed the user version side-by-side with the system version with no problems. The basic differences between the two is that the system version installs on the file system like every other app. The user install is basically a click-once (or web installer) version that installs in the User folder of the machine.
The settings made to VS Code in the system version save for Everybody on the computer and the user version the settings are only for the user. I find that the behavior of the user version is a bit annoying for me because I have reasons to want to open multiple copies of VS Code at the same time and the user version only allows one instance. Otherwise, there's not really anything different between the two as far as I can tell.
Many companies (like mine) dont allow Admin privileges, I think that's the main point so you can still install VSC with the user installer
After user version of Visual Studio Code is downloaded, make cmd in the download folder and run a command below, replacing the correct version in the VS ode installation file name:
runas /trustlevel:0x20000 ./VSCodeUserSetup-x64-1.74.3.exe
start the command below in order to check which trust levels are supported:
runas /showtrustlevels

installing an application from a command line on a mac

installing an application from a command line on a mac
Hope someone can help.
I need to reinstall Final Cup Studio 2 on my mac. Since I've change to the new operating system: Lion, I'm not able to reinstall the application from the installations disks because PowerPC applications are no longer supported with Lion. One suggested solution, seems to work with many people, is to instal the program from the command line with the following argument:
$ sudo installer -package /Volumes/Final\ Cut\ Studio/Installer/FinalCutStudio.mpkg -target /
After what appear to be a "successful installation", the program is no where to be found :(.
Another solution was to add the specific PATH to were the application/s are going to reside:
/Volumes/[MainDrive]/Applications/
The problem with this is that I don't know hoy to add the additional information to the command line.
I've created a subfolder named: FINALCUTSTUDIO2 under the Applications Folder and would like to give a command to install the applicationto that particular
Rosetta, the program that lets you run PowerPC binaries on Intel processors, was taken out of OS X starting with Lion. There's no way to make it run on Lion, unfortunately, even if you got it installed somehow.

How to enable autocomplete in GoClipse?

The instructions how to install GoClipse have been followed.
I'm not getting any autocomplete stuff happening at all, either for local packages that I write, for built in stuff, or for GAE stuff (I have downloaded Go src to the SDK folder as the wiki states).
Are there any settings that I can check to ensure it is set up correctly? Is autocomplete supposed to work in the current version?
As the GoClipse with AppEngine article you linked to says:
We assume the reader has a working copy of GoClipse running in their Eclipse environment.
so that’s not the article you want to refer to. Instead, check for GoClipse.
The auto completion is named content assist in eclipse. The GoClipse features state:
Now delivered with content assist via Gocode for Windows, OS X 64bit, and Linux 64bit.
Gocode is an auto-completion daemon. So you will also have to install and run that one besides your eclipse + GoClipse.
There is a bug in the current version of Goclipse for the Linux platform. It currently delivers a prebuilt version of gocode for Windows, 64 bit OS X, and 64 bit Linux. I have only been able to test it locally with limited resources, so I really depend on users to report the problems they find at:
http://code.google.com/p/goclipse/issues/list
If you are having problems, I urge you to download and install gocode into your $GOROOT/bin directory and see if that helps. Otherwise, the fix will come in the next release in a few days.
Also, sorry for causing you any trouble and thank you for trying Goclipse.
If you are not using a gocode upstream (but the one shipped with Eclipse) on Linux you are also no be able to build your application with CRTL+F11, although just clicking in Run->Run is going to work.
So, I strongly recommend to update your gocode on Linux, as simple as:
$ sudo GOPATH=/opt/go/ go get -u github.com/nsf/gocode

How to remove old versions of iPhone SDK when installing the new one?

I have downloaded iPhone SDK 4.0.2, I wanted to install it, but it looks that I don't have enough space. This made me think that maybe I could unistall the previous versions of iPhone SDK and install only the newest one.
Does anyone know how to do this?
Should I keep the old versions? Is there any situation they could be useful?
Thanks for sharing your thoughts!
Should you remove old versions? Up to you. You'll certainly have a "clean" installation. Do whatever you think is best for you. (You might want to reboot your system after uninstalling.)
Paul Peelen linked the command line step to do the removal, but I'm going to quote ad verbatim from Apple's "About Xcode.pdf" since the link could disappear:
Uninstalling Xcode Developer Tools
To uninstall Xcode developer tools on the
boot volume along with the
directory, from a Terminal window
type:
$ sudo <Xcode>/Library/uninstall-devtools -mode=all
To remove the underlying developer content on the boot volume,
but leave the directory and
supporting files untouched, from a
Terminal window type:
$ sudo <Xcode>/Library/uninstall-devtools --mode=systemsupport
To just remove the UNIX development support on the
boot volume, but leave the
directory and supporting files
untouched, from a Terminal window
type:
$ sudo <Xcode>/Library/uninstall-devtools --mode=unixdev
Finally, to just uninstall the directory you
can simply drag it to the trash, or
from a Terminal window type:
$ sudo <Xcode>/Library/uninstall-devtools --mode=xcodedir
NOTE: The uninstaller that ships with previous versions of
the Xcode developer tools will not
clean everything off of your system
properly. You should use the one
installed with these Xcode developer
tools.
(Those are current at least as of "Xcode 3.2.3 for Mac OS X 10.6 and iPhone OS 4.0")
You can use appzapper, or just remove the stuff in /Developer/Applications (I believe).
Edit:
Asked my friend google, and this is what it came up with: http://macdevelopertips.com/xcode/how-to-uninstall-xcode.html
The new iOS SDK overwrites most of the old one (unless you change the installation directory), so it doesn't really double the disk space usage.