I don't necessarily think we want to tell people to go in and start making changes to the main package.  For example, a user is not going to be able to do that if the package is installed globally, unless they su to root to go make the changes.  It's not really the node way.

I feel like, if we want to have an explicit target for users to simply generate a working copy of the sample apps, we should piggy back on the existing functionality for creating a new app, in one of two ways:

1. Go through the workflow to create a new app, minus creating the new app.  Essentially, ask the user for an output directory, then just do the step of app creation that copies the Mobile SDK to that specified folder.  Then give them the standard instructions at the end.
2. Make the 'samples' target be an output-only step, like it currently is, except tell the user to create their own app, then access the samples that are created with it.

Bonus points for either one of these processes automatically running the appropriate steps to update the projects after they've been copied over.  We really should do this; there's very little reason that I can see to continue to make the user run these post copy project update steps themselves.