On May 28, 2018, at 21:10, Zero King wrote:
> Hi,
>
> On Thu, May 10, 2018 at 03:58:11PM +1000, Joshua Root wrote:
>> Source code and pkgs for MacPorts 2.5.0-beta1 are now
>> available [1]. Testing of either of these install methods is helpful.
>
> Now that 2.5.0 is released, we should protect
Hi,
On Thu, May 10, 2018 at 03:58:11PM +1000, Joshua Root wrote:
Source code and pkgs for MacPorts 2.5.0-beta1 are now
available [1]. Testing of either of these install methods is helpful.
Now that 2.5.0 is released, we should protect the release-2.5 branch in
macports-base to disable force pu
On May 26, 2018, at 14:38, Ken Cunningham wrote:
> On May 26, 2018, at 12:27 PM, Ryan Schmidt wrote:
>
>> The error occurs when there is a mismatch between which C++ standard library
>> a port says it uses (by setting configure.cxx_stdlib, or by leaving it set
>> to its default value) and whic
> On May 26, 2018, at 12:27 PM, Ryan Schmidt wrote:
>
> The error occurs when there is a mismatch between which C++ standard library
> a port says it uses (by setting configure.cxx_stdlib, or by leaving it set to
> its default value) and which C++ standard library it actually links with.
>
> On May 26, 2018, at 9:40 AM, Ryan Schmidt wrote:
>
> Unfortunately, we have no way to tell Xcode to use one of our compilers. I
> believe we need to create some kind of Xcode-specific file to tell it about
> each of our compilers, then update the xcode portgroup to use that. Nobody's
> do
On May 26, 2018, at 14:25, Ken Cunningham wrote:
> On May 26, 2018, at 9:49 AM, Ryan Schmidt wrote:
>
>> On May 26, 2018, at 11:48, Ken Cunningham wrote:
>>
>>> Well I think you did the cmake finaggeling last time Not sure you could
>>> find a better way, but I wait to see...
>>
>> I don'
> On May 26, 2018, at 9:49 AM, Ryan Schmidt wrote:
>
>
> On May 26, 2018, at 11:48, Ken Cunningham wrote:
>
>> Well I think you did the cmake finaggeling last time Not sure you could
>> find a better way, but I wait to see...
>
> I don't recall what you're referring to.
if {!((${os.pla
On May 26, 2018, at 11:48, Ken Cunningham wrote:
> Well I think you did the cmake finaggeling last time Not sure you could
> find a better way, but I wait to see...
I don't recall what you're referring to.
Well I think you did the cmake finaggeling last time Not sure you could
find a better way, but I wait to see...
K
Sent from my iPhone
> On May 26, 2018, at 9:40 AM, Ryan Schmidt wrote:
>
>> On May 26, 2018, at 11:15, Ken Cunningham wrote:
>>
>>> On May 25, 2018, at 12:05 PM, Ryan Schmid
On May 26, 2018, at 11:15, Ken Cunningham wrote:
> On May 25, 2018, at 12:05 PM, Ryan Schmidt wrote:
>
>> It's "broken" in that it links with libstdc++, even though MacPorts believes
>> it will link with libc++ on your system. The rev-upgrade code in previous
>> versions of MacPorts did not che
> On May 25, 2018, at 12:05 PM, Ryan Schmidt wrote:
>
> It's "broken" in that it links with libstdc++, even though MacPorts believes
> it will link with libc++ on your system. The rev-upgrade code in previous
> versions of MacPorts did not check for this kind of "broken".
>
> Fix it by fixin
On Fri, May 25, 2018 at 02:05:00PM -0500, Ryan Schmidt wrote:
On May 25, 2018, at 12:57, Zero King wrote:
On Thu, May 17, 2018 at 11:36:39PM +1000, Joshua Root wrote:
It's been a week with no new tickets filed against base. I'll give it
one more week and then, if nothing comes up, tag a relea
On May 25, 2018, at 12:57, Zero King wrote:
> On Thu, May 17, 2018 at 11:36:39PM +1000, Joshua Root wrote:
>> It's been a week with no new tickets filed against base. I'll give it
>> one more week and then, if nothing comes up, tag a release candidate.
>>
>> - Josh
>
> I tried the rc1, and unar
Hi,
On Thu, May 17, 2018 at 11:36:39PM +1000, Joshua Root wrote:
It's been a week with no new tickets filed against base. I'll give it
one more week and then, if nothing comes up, tag a release candidate.
- Josh
I tried the rc1, and unar is now "broken". How can I fix it?
unar is using libst
It's been a week with no new tickets filed against base. I'll give it
one more week and then, if nothing comes up, tag a release candidate.
- Josh
Source code and pkgs for MacPorts 2.5.0-beta1 are now
available [1]. Testing of either of these install methods is helpful.
Be prepared to encounter bugs. As always, having a recent backup would
be wise. Please report any bugs that you find [2] (after first searching
Trac [3], of course!)
There a
16 matches
Mail list logo
