WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
On Feb 24, 2012, at 2:55 PM, Jeremy Lavergne wrote:
>> I'm honestly not sure, sorry. I did file a radar asking for a better command line interface to accepting and checking the status of acceptance, and that should work for your needs, but unfortunately that doesn't quite help with the released product =/
> It happens, sometimes more than not :-)
> The other thread indicated the "accepted for everyone" approach is what we'd like to avoid for legal reasons, so I think MacPorts plans to make due with the user plist copying.
Despite the tenor of that thread, I'm far more concerned that we don't put speed bumps in the way of the user. Adopting their existing preferences is a reasonable way to be pretty certain that they've already accepted the agreement, as they've likely run the Xcode GUI. It cuts way down on the number of people who won't be able to tell what's going on, and to whom we would have to explain to run some separate command to accept the preferences.
<rant>Ideally, there would be a way to check if the license has been accepted for a given user. Even more ideally, that stupid command line license agreement wouldn't be in the command line tool. It's got to be one of the stupidest, most big-company-bureaucratic things I've ever seen. But I guess I can't deny that Apple is now big-company, can I? I mean, what are they protecting by making you accept a license agreement to run xcodebuild from the command line? What are they protecting that you don't already agree to when you download Xcode, or join the developer program, or run any number of other command line tools? Frankly, I don't know, because like 99% of users I haven't read the agreement, even though I've accepted it, a fact that makes click-through licenses like this hard to enforce in court. </rant>