Re: Migration Assistant moved MacPorts home directories

On 2 Mar 2017, at 01:21, Brandon Allbery wrote: > In fact only one change is needed: you do some of the early steps on the > origin system instead of all of it on the destination. I've used an adjusted > version of that a few times to do migrations, including with Apple's > Migration Assistant

Re: Migration Assistant moved MacPorts home directories

On 2017-03-02 00:34, Brandon Allbery wrote: > > On Wed, Mar 1, 2017 at 6:10 PM, Ryan Schmidt > wrote: > > I'm not talking about an unusual case. I'm talking about the > completely normal case that I expect all users will undergo when > moving to a new

Re: Migration Assistant moved MacPorts home directories

> On Mar 1, 2017, at 5:26 PM, Bradley Giesbrecht wrote: > >> On Mar 1, 2017, at 4:13 PM, Ryan Schmidt wrote: >> I'm just unclear why I'm the first to report this problem. Has nobody used >> migration assistant? Or has everybody just ended up with broken >> installations and either not realize

Re: path to sources.conf?

Thanks y'all. On 2/28/17 9:49 PM, Joshua Root wrote: Dave Horsfall wrote: On Tue, 28 Feb 2017, Ryan Williamson via macports-users wrote: Try "sudo find / -name sources.conf" Or better still, use the "locate" command (and run locate.updatedb every so often). As of 2.4.0 we have some shiny

Re: Migration Assistant moved MacPorts home directories

> On Mar 2, 2017, at 08:52, m...@macports.org wrote: > > >> On Mar 1, 2017, at 5:26 PM, Bradley Giesbrecht wrote: >> >>> On Mar 1, 2017, at 4:13 PM, Ryan Schmidt wrote: >>> I'm just unclear why I'm the first to report this problem. Has nobody used >>> migration assistant? Or has everybody ju

Re: Migration Assistant moved MacPorts home directories

> On Mar 2, 2017, at 08:02, Rainer Müller wrote: > > On 2017-03-02 00:34, Brandon Allbery wrote: >> >> On Wed, Mar 1, 2017 at 6:10 PM, Ryan Schmidt > > wrote: >> >>I'm not talking about an unusual case. I'm talking about the >>completely normal case that