Joshua Root

Ports that do that must be using the C++ compiler to link, presumably. Does this simpler approach work? ``` configure.ldflags-append {*}${configure.cxxflags} ```

On 2019-4-20 07:43 , Arjun Salyan wrote: > @umeshksingla : yes, it takes > "forever" to build it for the first time. > > That is because it has to...

The portindex script does use the portdir to check whether Portfiles have been indexed already and skip them if so, yes.

> We could merge everything up to and including "macports1.0: Sort and format list of options", and merge the rest later? Sounds good. Remember to add the .gitignore changes first....

> The configure script already removes the given prefix from PATH. The CC=... must have been added for unrelated reasons. https://trac.macports.org/ticket/23095 https://trac.macports.org/ticket/30009#comment:1

> I recommend to prepare the update of libjasper port and wait a little bit to see if all is fine from client code. Certainly; that's the purpose of this...

These ports need build fixes due to jasper changes: exact-image, libdevil, wgrib2, [xv](https://github.com/jasper-software/xv) These ports were already failing before this change: ResIL, gstreamer010-gst-plugins-bad, digikam, kdelibs4 (maybe?), kopete, metview qt*-qtimageformats need...

I'm not totally sold on the wording and it being an error, since it doesn't actually break anything, it just makes it inconvenient to specify the version. I certainly agree...

Moving conversation from #211. > In terms of sharing the data and logic, can the MacPorts infrastructure scripts utilize MacPorts base? Sure. That has the (perhaps minor) drawback that it...

> Certainly, and we wouldn't want to be tied to a MacPorts base release. To eliminate that, could we simply migrate most of the core logic to `_resources`? The drawback...