This request is in contradiction to the change that SC should be installed for the current user only: as we don't want the user to require to log in as an administrator during installation, we can't install the StartupItem. StartupItems are system wide. Therefore only an administrator can install them.

The following change would do what we want, if the installer was run as an administrator:

Index: Installer/install.sh
===================================================================
--- Installer/install.sh        (revision 24067)
+++ Installer/install.sh        (working copy)
@@ -54,6 +54,10 @@
 
 if [ -e "$2" ] ; then
        cd "$2/Contents/server"
+
+       # install SC to start at boot time
+       sudo -b -H -u $USER "../Resources/create-startup.sh"
+
        sudo -b -H -u $USER "../Resources/start-server.sh"
 

I suppose a decision on what is more important needs to be made.  Since we removed the choice from the installer I see the two following options making the most sense.

1 Do NOT require an admin log in and install for the current user only and set automatically start to when I log in.

2 DO require an admin log in and install for all users and set automatically start to when system boots.

Now that bug 9932 appears to be fixed this should not be a technical decision just an expected behavior one.

Dean, your thoughts?

Adding Dan to comment.

Ultimately... long-term... if we make these choices for the user we need a button on the summary screen when it states, "SC will be installed with these settings," that a user could click to make changes.

However, I know that can't happen for 7.3.

We do get customers with multiple users on their Mac who want to play music regardless of who's logged in.  That would suggest we need "All Users" as the default.  It also seems like the safer choice in that it has more power rather than less.  (however, it certainly is VERY easy to install for "all users" by installing manually if we default to "this user only".)

One thing though:  no matter what we choose the Setup Wizard needs to open automatically after installation is done.  We do this on Windows now.

Having the server run at boot time is a very reasonable default behavior.  If it requires a password, the let's ask for it and get them on their way to the wizard.

Dan: Note that having it installed as one user vs multiple users only affects whether one or all users see the server in their preference pane, not whether multiple libraries are available.  The server is always run by the user who installed/configured the software. 

The basic goal here is to reduce the number of steps and decisions that a typical user will need to go through in order to get up and running, and removing the all users/one user decision, the boot/login/none decision, the manual start in the preference pane all work toward these goals.

If a user wants to go back and customize their settings, then the System Preferences are a reasonable way to do this...

change 24104
- installation requires admin password
- install for all users
- install to run at boot

Installer still defaults to "Never" for Automatically run.  I downloaded 24106, last night's build.

I'd also like to know what advantage or benefit we gain by installing for "All Users"?  It seems now like the answer is "none".

If that's the case, then let's install for "single user", avoid the password nonsense, and make it easier for the customer-- which is our ultimate goal here.  (also note, if we install for "All Users" the customer has to enter their password to *uninstall* SqueezeCenter as well.  more complication.)

Hmm... it does work on reboot though. Is this a UI issue only?

And concerning global install or not: we can't boot at startup without the "password nonsense". This has been discussed in this very bug report.

Understood.  Sorry if I missed that.

I'm mostly concerned with what benefit we gain from our change.  For example, we now auto-select "run at login" for all Windows users.  That change was made many months ago.  In the name of consistency do we also want that default for Mac?  And if not, I'm only wondering why?

I have no problem with requiring a password for installing *if* it provides a benefit to the customer and/or us.  If it doesn't, then it seems needless.

We had to make it run at login on windows because of a limitation on windows. 

Having it run automatically at boot is better because it can be done without any user intervention.  they can adjust this behavior if they want from the pref pane.

It seems that the Automatically start: option in the prefrence pane is actually completely ignored now.  I can change it to never or when I log in and SqueezeCenter will still start at system boot.

Hmm... if I manually set it to Boot, I'm asked for the admin's password. After this I can change it to other modes. But not before doing so.

change 24126
- only configure SC to run at boot if this is a first time installation
- set the startup type button's default to Start At Boot

Issue seems to have been that the installer _always_ installed to start at boot, even if it had previously been configured not to do so. The PrefPane otoh didn't know about this, as the installer did not update the preference file. I changed it so that the installer won't change anything if a startup mode pref is already on the system (check ~/Library/Preferences/com.slimdevices.slim.plist). This will hopefully fix the odd behaviour we've seen with yesterday's build.

Thanks Michael, this appears to be fixed now and closing as such.

This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.

Reduce number of active targets for SC