Thanks a bunch for the info. I'll talk to my WWDR - this bit has always
confused me. I wish I had thought of it at WWDC, we had a meeting last
week. I usually just talk to people in the dev program anyway, but I'd like
to know what help I can give and how publicly.
—Mark
___
On Sun, Jun 19, 2016 at 10:52 PM, Jeremy Huddleston Sequoia <
jerem...@apple.com> wrote:
>
> > On Jun 19, 2016, at 17:15, Mark Anderson wrote:
> > Further, Apple agrees that You will not be bound by the foregoing
> confidentiality terms with regard to technical information about
>
Although that is in fact what happened, it was more because thousands of public
beta users chose to ignore the NDA, probably because they didn't really read or
understand it. Apple hosts on the Apple Support Community Forum were quick to
delete all postings in violation, but that was really the
> On Jun 19, 2016, at 17:15, Mark Anderson wrote:
>
> Jeremy, I'm still interested in a answer as to what is covered by this:
>
> Further, Apple agrees that You will not be bound by the foregoing
> confidentiality terms with regard to technical information about pre-release
>
Jeremy, I'm still interested in a answer as to what is covered by this:
Further, Apple agrees that You will not be bound by the foregoing
confidentiality terms with regard to technical information about
pre-release Apple Software and services disclosed by Apple at WWDC (Apple’s
Worldwide
Sent from my iPhone...
> On Jun 19, 2016, at 13:55, Bachsau wrote:
>
>
>> Am 19.06.2016 um 05:24 schrieb Jeremy Huddleston Sequoia
>> :
>>
>> As a reminder, macOS 10.12 Sierra has only been released as a developer
>> preview to developers and is
> Am 19.06.2016 um 05:24 schrieb Jeremy Huddleston Sequoia :
>
> As a reminder, macOS 10.12 Sierra has only been released as a developer
> preview to developers and is covered by an NDA.
Ever heard of something called "free speech"? The snowden leaks were also
covered by
Sent from my iPhone...
> On Jun 19, 2016, at 07:18, Artemio González López wrote:
>
> Thanks a lot, Jeremy!
>
> As I said in a previous message, I wasn't aware that I may be violating the
> nondisclosure agreement, which of course it wasn't my intention. In fact,
> right
Thanks a lot, Jeremy!
As I said in a previous message, I wasn't aware that I may be violating the
nondisclosure agreement, which of course it wasn't my intention. In fact, right
after posting I realized that the problem was that I hadn't selected Xcode 8
using xcode-select. After doing that, I
> On Jun 18, 2016, at 21:13, Al Varnell wrote:
>
> Unless somebody can show that Apple announced at WWDC the results of
> attempting to migrate MacPorts to Sierra, then no, it does not allow a
> discussion such as this. The exemption was only meant to cover Sierra
>
On 19 June 2016 at 06:13, Al Varnell wrote:
>
> That being said, I was under the impression that before we can attempt to
> migrate from an older OS, we must wait for MacPorts to release a Sierra
> version of the MacPorts installation package.
No, that's not a requirement. You can of course try
Unless somebody can show that Apple announced at WWDC the results of attempting
to migrate MacPorts to Sierra, then no, it does not allow a discussion such as
this. The exemption was only meant to cover Sierra capabilities announced at
WWDC, not the results of actually using it, including what
As a reminder, macOS 10.12 Sierra has only been released as a developer preview
to developers and is covered by an NDA. Please do not discuss it on this list.
If you have issues, please feel free to reach out to me directly.
In this case, you forgot to install the Xcode command line tools
Hi,
On Wed, Jun 15, 2016 at 10:09:22PM +0200, Artemio González López wrote:
> checking for Apple Foundation library... no
This check should not have failed for you. Please provide config.log.
Additionally, try compiling the following program and provide the output
(which will likely also be
I’ve installed the Developer preview of macOS 10.12 Sierra, and I have been
trying to rebuild my MacPorts installation following the Migration instructions
at MacPorts. The problem is that ./configure —enable-readline fails with the
error message found at the end of the complete output of this
15 matches
Mail list logo