On Tue, 18 Sep 2018 10:53:19 -0500 Ryan Schmidt
wrote:
> The minimal changes to have MacPorts recognize Xcode 10 were
> committed in June:
[...]
> The base change was included in MacPorts 2.5.3 released in July.
>
> I don't know if Xcode 10 introduces any changes that would impact
> MacPorts. An
I'll second that having a CoC isn't a bad idea. I like the shorter version <
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html >, which
leaves room for our project to implement various parts as we see fit (the
PostgreSQL CoC is, in my opinion, a little too specific in some
On Sep 17, 2018, at 21:55, Ken Cunningham wrote:
> I’m about to archive my current high sierra setup into a VM, and if possible,
> I’d like it to match the way the buildbot will be finally left.
>
> 10.13 with XCode 9?
>
> or
>
> 10.13 with Xcode 10?
>
> I guess people who stay on 10.13
On Sep 17, 2018, at 19:39, Perry E. Metzger wrote:
> Are we currently set up for the new Xcode 10? It was officially
> released today, although Mojave won't show up for another week.
The minimal changes to have MacPorts recognize Xcode 10 were committed in June:
On Sep 18, 2018, at 09:55, Jackson Isaac wrote:
> Lately, I have seen open source projects have started adopting Code of
> Conduct. [1], [2]
>
> I think it is a great step to keep the open source community healthy
> and welcoming to everyone.
>
> I would like to know what other developers
On Tue, Sep 18, 2018 at 11:53 AM Ryan Schmidt
wrote:
>
>
> On Sep 17, 2018, at 19:39, Perry E. Metzger wrote:
>
> > Are we currently set up for the new Xcode 10? It was officially
> > released today, although Mojave won't show up for another week.
>
> The minimal changes to have MacPorts
On Sep 18, 2018, at 10:53, Ryan Schmidt wrote:
>
> An area of possible concern for High Sierra is if Xcode 10 removes the same
> 32-bit parts that macOS Mojave removes.
The Xcode 10 release notes confirm that it does remove the 32-bit parts from
the macOS SDK:
Yeah. I’ve had to run all my builds with-universal since
the beta on XCode 10 / 10.14
On Tue, Sep 18, 2018 at 1:39 PM Ryan Schmidt
wrote:
>
>
> On Sep 18, 2018, at 10:53, Ryan Schmidt wrote:
> >
> > An area of possible concern for High Sierra is if Xcode 10 removes the
> same
More feedback from the developer:
> Supposing that a profile.dat is available in csl/generated-c (as it is when
> one has fetched from subversion, and it will be in some future snapshots, but
> is NOT in the files you unpack from the .tar file in the mac snapshot
> directory unless you may
Apple has announced [1] that macOS Mojave (10.14) will be released on September
24, 2018. It will require Xcode 10, which has already been released.
If you have not yet been testing the macOS Mojave public beta, and you have a
spare machine or disk you could install it on, you may want to do so
The current src for reduce now builds a reduce.app that you should be able to
double-click to open. Should this be moved to the Macports Applications
folder? There is also a script "redcsl" which must be stored adjacent to
reduce.app. A command "redcsl" issued from terminal should open the
I'm fairly new in the MacPorts community, but I'd like to offer an
opinion on this topic. Personally, I feel that CoC's like the
Contributor Covenant, Postgres CoC, FreeBSD CoC, etc. are very... umm,
let's just say strict. I think they read more like license terns than a
set of guidelines on how
On Mon, 10 Sep 2018 12:15:37 -0700 Michael
wrote:
> Is there a way to tell CPP to only expand compile-time determinable
> #ifdef's, and not macro expansion? The standard IO library, for
> example, gets pretty hard to read once expanded.
there's a program out there called "unifdef" that might be
Thank you, Perry!
I see it’s right there in Xcode — I just never noticed it before. That (at
present) is likely about as close as I will get to what I want.
Ken
> On Sep 18, 2018, at 5:11 AM, Perry E. Metzger wrote:
>
> On Mon, 10 Sep 2018 12:15:37 -0700 Michael
> wrote:
>> Is there a way
On Sep 17, 2018, at 17:01, Mark Brethen wrote:
> Adding "-lintl" to configure.ldflags seems to have worked however new errors
> popped up:
>
> :info:build make[3]: *** No rule to make target
>
Yep, here is his response:
> Aha - when I look at your macports log you do not seem to be fetching Reduce
> from subversion, you are fetching a source .tar file for it. Well that has
> not up to now contained profile.dat because one can regenerate what is needed
> by going (in a build
On Sep 18, 2018, at 08:25, Mark Brethen wrote:
> Yep, here is his response:
>
>> Aha - when I look at your macports log you do not seem to be fetching Reduce
>> from subversion, you are fetching a source .tar file for it. Well that has
>> not up to now contained profile.dat because one can
Lately, I have seen open source projects have started adopting Code of
Conduct. [1], [2]
I think it is a great step to keep the open source community healthy
and welcoming to everyone.
I would like to know what other developers think about this. Also, who
would be the decision makers (PortMgrs?)
18 matches
Mail list logo
