Re: path to sources.conf?

2017-04-03 Thread Michael Parson
On Wed, 1 Mar 2017, 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). Or better still, since we're on Macs and have Spotlight indexing

MP_EDITOR doesn't work

2017-04-03 Thread db
I set MP_EDITOR but it doesn't seem to work on base 2.4.1. VISUAL, second var MP checks according to the guide, does though.

Re: building from source with libc++

2017-04-03 Thread db
On 3 Apr 2017, at 18:09, Mojca Miklavec wrote: > Basically yes. You could follow point 3 of > https://trac.macports.org/wiki/Migration Is the script from 3.e. relevant if no particular variants were installed? I ask because I probably won't automate the whole process as I might have to check s

Re: building from source with libc++

2017-04-03 Thread Mojca Miklavec
On 2 April 2017 at 21:06, db wrote: > >> Usually the >> biggest problem is C++11 nowadays and libc++ usually helps there, it's >> just that most developer don't have resources to actually test >> packages on older boxes. > > Re libc++, how would you go about it? Echo requested, uninstall installed,