[MacPorts] Migration modified

[Dave Yost]

> On 2014-12-14, at 07:59 PM, Lawrence Velázquez <larryv at macports.org> wrote:
> 
> The migration steps weren't really intended to be run as a single script. I'm not comfortable telling users to run this big untested blob of code.

Then let’s test it! Works for me on Yosemite. I’ll run it again.

You could put in a caveat that one can run the commands interactively if one is worried about it.

Really, code to do a migration should be part of macports, IMO. Nothing like being able to start a command and walk away for a couple of hours and have it do everything without tweaking.

Dave

> 
> 
>> On Dec 14, 2014, at 10:37 PM, MacPorts <noreply at macports.org> wrote:
>> 
>> Page "Migration" was changed by dave at yost.com
>> Diff URL: <https://trac.macports.org/wiki/Migration?action=diff&version=80>
>> Revision 80
>> Comment: Use a single sudo, so only one password is required.
>> Changes:
>> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>> Index: Migration
>> =========================================================================
>> --- Migration (version: 79)
>> +++ Migration (version: 80)
>> @@ -23,29 +23,36 @@
>>   {{{
>>   # If there is an argument, then don't preserve 'requested' flags.
>>   function reinstallPorts() {
>> -      dontPreserveRequestedFlags=$1
>> +      local -r dontPreserveRequestedFlags=$1
>> +      set -e
>> +      # This will fail if xcode-select needs to be run.
>> +      clang --version
> 
> What is the point of printing the Clang version? And you don't know which "clang" is being run.

I was looking for a command I could run to smoke out wither code-select is going to have to run before port can do its work.