Migration question and binary question
Ryan Schmidt
ryandesign at macports.org
Fri May 9 06:10:01 PDT 2014
On May 9, 2014, at 02:22, Jerry wrote:
> On May 8, 2014, at 10:39 PM, Joshua Root wrote:
>
>> Jerry wrote:
>>> I am considering using the "Automatically reinstall ports" suggestion whereby a script is downloaded which script then works with a previously saved myports.txt. If I do this, will the script install old versions of ports which had not been active? I'm thinking that this might be a good time to do some decrufting and I would like to consider these old inactive versions as mostly cruft and not reinstall them.
>>
>> As Ryan said, it can only install the current version of each port. But
>> if you have a port installed with different variants, it will reproduce
>> that. E.g. if you start with this:
>>
>> foo @1.0_0
>> foo @1.0_0+bar (active)
>> foo @1.1_0
>>
>> then if 1.1 is the current version of foo, after running restore_ports
>> you will have:
>>
>> foo @1.1_0+bar (active)
>> foo @1.1_0
>>
>> After you generate myports.txt, it's worthwhile to glance through it and
>> delete any lines you don't want any more, as well as to adjust some of
>> the variants if desired, as Brandon suggested.
>
> Thanks for all the help, everyone!
>
> I think I'm going to install manually, at least at first, and see how that goes. The problem with combing through myports.txt to figure out what I don't need any more is that most of the stuff there I don't recognize, being dependents of things I do recognize.
If you don't personally need a port, you can remove it from the list. If MacPorts needs it as a dependency, it'll be installed again automatically.
More information about the macports-users
mailing list