Thanks, I’ll check those other items out.

Jim
Seattle, WA

> On May 7, 2022, at 11:24 AM, [email protected] wrote:
> 
> Sorry I did not address your question. Though I've never tried that method, 
> my understanding is that everything MacPorts is in /opt/local owned by 
> root:wheel and 755, so I have always assumed, for at least a decade now, that 
> what you intend should just work, because I've had those thoughts before as 
> well, I just prefer to watch code build for days rather than copy a folder 
> for a few minutes.
> 
> I always backup macports.conf separately, along with .bash_profile (not 
> really part of MacPorts but sourcing it keeps $PATHs how I want them).
> 
> Also, for the system proper, I install everything that is not required to be 
> installed in /Applications into ~/Applications, so when migrating I just copy 
> over my user folder and then nearly all my applications are already installed.
> 
> Which reminds me, you may have some MacPorts application builds in 
> /Applications/MacPorts
> 
> 
> 
> 
>> On May 7, 2022, at 14:10, James Secan <[email protected]> wrote:
>> 
>> Should have mentioned I’ve already done that as my final fall-back, but I’d 
>> rather be able to get back to exactly where I was vis-a-vis MacPorts if I 
>> step on something I shouldn’t have.
>> 
>> Jim
>> Seattle, WA
>> 
>>> On May 7, 2022, at 11:00 AM, [email protected] wrote:
>>> 
>>> May want to save a copy of output of
>>> 
>>> port list requested
>>> 
>>> to make it easy to restore if it all goes South. When I'm migrating, I take 
>>> that list and turn it into an install script.
>>> 
>>>>> On May 7, 2022, at 13:55, Jim Secan <[email protected]> wrote:
>>>> 
>>>> I’m about to embark on a major mucking-out of my MacPorts installation on 
>>>> an El Capitan system.  I believe that if I make a copy of /opt/local that 
>>>> gives me everything I need to recover if I find myself with a non-working 
>>>> setup after this process.  Is that right, or are there other directories I 
>>>> should backup as well?
>>>> 
>>>> Jim
>>>> Seattle, WA
>>>> 
>> 

Reply via email to