Hi,
Motivated by https://trac.macports.org/ticket/54749 and the recent
change in upstream GnuPG 2.1.x and the new 2.2.0 to install as "gpg"
instead of "gpg2" I would like to start a discussion about the future of
all the GnuPG ports and how to address the inevitable issues that will
arise
On 2017-09-04, at 1:43 AM, Ryan Schmidt wrote:
>
> I have not followed the development of the cxx11 1.1 portgroup so I don't
> know the benefits and drawbacks of using it compared to using libc++.
After digging into this for a year and debugging and fixing a _great many_
ports, here are my
Hi Aaron,
I'm not a MacPorts maintainer, but one of MacPorts’s features is that building
custom ports is very easy, especially compared to other port implementations.
If you’re familiar with git, create a local branch of the ports tree and add
custom ports to your heart's content. Once you’ve
Hi all.
I was wondering if there was any official guidance on what kinds of software
was appropriate for inclusion in MacPorts, beyond the phrase "command-line, X11
or Aqua based open-source software” on macports.org.
Specifically I have two things that seem borderline inappropriate, but that
On Sep 4, 2017, at 04:25, Mojca Miklavec wrote:
> On 4 September 2017 at 10:47, Ryan Schmidt wrote:
>> On Sep 2, 2017, at 11:25, Rainer Müller wrote:
>>
>>> * archivefetch does not yet respect cxx_stdlib in any way
>>
>> Yeah that would need adjustment, based on how we decide to differentiate
On 4 September 2017 at 10:47, Ryan Schmidt wrote:
> On Sep 2, 2017, at 11:25, Rainer Müller wrote:
>
>> * archivefetch does not yet respect cxx_stdlib in any way
>
> Yeah that would need adjustment, based on how we decide to differentiate
> libc++ archives from libstdc++ archives.
Is there any
On Sep 2, 2017, at 11:25, Rainer Müller wrote:
> The following goes beyond your GSoC project, but I think it fits into this
> discussion. Back in May, I published an experiment on my GitHub repo that I
> had
> lying around. This adds functionality to stores the cxx_stdlib option in
> registry,
> On Sep 3, 2017, at 16:16, db wrote:
>
> On 3 Sep 2017, at 13:47, Rainer Müller wrote:
>> The other option to switch would be to just change the default of
>> cxx_stdlib with the next 2.x release, wipe all existing binary packages
>> and ask all