Re: opensource.apple.com mirror propagation status?

> On Mar 28, 2017, at 14:40, Thomas Nilefalk wrote: > > I got a problem updating my installation because ld64 was requested at 274.2 > could not be found. It turned out that it was only available on > opensource.apple.com and for some reason that has been 403:ed for Swedish > users ( opensour

Re: Check for binaries

There is also this: https://packages.macports.org/ which will show you which prebuilt packages exist. eg https://packages.macports.org/qt4-mac/ that might help you out as well. K On 2017-03-28, at 1:34 PM, Adam Dershowitz wrote: > Is there any way to check if a specific port will be instal

Re: Check for binaries

So, I guess I could do that, and then cancel if it starts to download. That’s a bit of a work around, but should do the job. --Adam > On Mar 28, 2017, at 4:48 PM, Ken Cunningham > wrote: > > you can specify in your macports.conf, or on the command line for one-offs, > that you only want t

Re: Check for binaries

> On Mar 28, 2017, at 4:42 PM, Brandon Allbery wrote: > > On Tue, Mar 28, 2017 at 4:34 PM, Adam Dershowitz > wrote: > Is there any way to check if a specific port will be installed as a binary or > built from source. > > The problem with this is that often the deci

Re: Check for binaries

you can specify in your macports.conf, or on the command line for one-offs, that you only want to install binaries. sudo port -b install my-big-port will install the binary if it exists, or abort. Ken On 2017-03-28, at 1:34 PM, Adam Dershowitz wrote: > Is there any way to check if a specif

Re: Check for binaries

On Tue, Mar 28, 2017 at 4:34 PM, Adam Dershowitz wrote: > Is there any way to check if a specific port will be installed as a binary > or built from source. The problem with this is that often the decision is made based on whether it can fetch a prebuilt binary: if the fetch fails, it builds fr

Check for binaries

Is there any way to check if a specific port will be installed as a binary or built from source. I’m looking for a flag that would just check if a binary is available for my particular configuration? I’m looking for something similar to “dry run” (-y). I did try -y on the hopes that it would

opensource.apple.com mirror propagation status?

I got a problem updating my installation because ld64 was requested at 274.2 could not be found. It turned out that it was only available on opensource.apple.com and for some reason that has been 403:ed for Swedish users ( opensource.apple.com 403s for users in swe

Re: building from source with libc++

On 28 Mar 2017, at 17:31, "Daniel J. Luke" wrote: > On Mar 28, 2017, at 9:55 AM, db wrote: >> Is there any MP official notice of support? > It's right there on https://www.macports.org That is not. And one thing is targeting mainly systems still supported by Apple, another going along with it a

Re: building from source with libc++

On Mar 28, 2017, at 9:55 AM, db wrote: > Is there any MP official notice of support? It's right there on https://www.macports.org "We provide a single software tree that attempts to track the latest release of every software title (port) we distribute, without splitting them into “stable” Vs.

Re: building from source with libc++

On 28 Mar 2017, at 13:15, Rainer Müller wrote: > The support in base is missing to differentiate between binary archives > with a different cxx_stdlib. That is required to provide an upgrade path > for existing installations. May I assume that that won't happen in the foreseeable future and start

Re: building from source with libc++

On 2017-03-28 11:00, db wrote: > On 27 Mar 2017, at 11:12, Mojca Miklavec wrote: >> Dealbreaker: >>https://trac.macports.org/ticket/50448 > > Thanks for pointing that out. I skimmed through it. > > What's the actual state re libc++ binaries for <10.9? The support in base is missing to diffe

Re: building from source with libc++

On 27 Mar 2017, at 11:12, Mojca Miklavec wrote: > Dealbreaker: >https://trac.macports.org/ticket/50448 Thanks for pointing that out. I skimmed through it. What's the actual state re libc++ binaries for <10.9? Is dropping support for <10.9 something MP team is considering? As a 10.8-user, M