It is true that they loosened the NDA two or three years back, but only that it
excludes any information that has already been made public (primarily via the
annual WWDC conference, but could also be otherwise made public through no
fault of your own, except that you may not post screen shots
I can open feedback via radar or whatever as I’m in the developer program
but also they loosened the NDA a bit a few years back. A bunch of us made
a fuss sometime after swift came out since it was vital to help each other
before the release. That’s why you can learn about SwiftUI and the like on
I would not be allowed to even say if I was, but my understanding is that
Feedback submissions from the public beta program are only considered in
aggregate and never responded back to individuals.
Sent from my iPad
-Al-
> On Jul 8, 2019, at 12:53, Peter Homann wrote:
>
> NDA.
MacBook running Sierra + all patches (it will *not* go further), XSANE
0.999.
The scanner is an Epson Perfection1240 (pretty old now) and XSANE stopped
seeing it around the time I upgraded to Sierra (or could have been a minor
update, as I rarely use it). USB info sees it, so it's not the OS
On 08/07/2019 15:57, Mark Anderson wrote:
> I am.
I am also.
signature.asc
Description: OpenPGP digital signature
I am.
On Mon, Jul 8, 2019 at 3:53 PM Peter Homann wrote:
> Anyone else on the MacOS beta program and now have Catalina? I have an
> issue I want to discuss, but without breaching the NDA.
>
> I have logged my issue through Apple's feedback process, but I would guess
> their first response will
Anyone else on the MacOS beta program and now have Catalina? I have an issue I
want to discuss, but without breaching the NDA.
I have logged my issue through Apple's feedback process, but I would guess
their first response will be that it isn't a MacOS problem, but a Macport
issue.
Thanks in
On Mon, 8 Jul 2019 at 14:27, Ryan Schmidt wrote:
>
> I don't think MacPorts will uninstall a port unless you tell it to (directly
> by name@version_revision+variants, or using a pseudoport (like "inactive" or
> "leaves"), or using port(1)'s "-u" flag).
>
> What could happen, though, is that
On Jul 8, 2019, at 07:34, joerg van den hoff wrote:
> On 08.07.19 14:27 , Ryan Schmidt wrote:
>
>> I don't think MacPorts will uninstall a port unless you tell it to (directly
>> by name@version_revision+variants, or using a pseudoport (like "inactive" or
>> "leaves"), or using port(1)'s
HEllo Rayan,
thanks for the link.
i will correct the address book then.
Raoul
> On 8 Jul 2019, at 12:42, Ryan Schmidt wrote:
>
>
>
> On Jul 6, 2019, at 11:27, rmgls wrote:
>
>> trying to build samba4 i get these errors,
>
> There are a few 6-year-old tickets open about the samba4
On Jul 8, 2019, at 06:10, joerg van den hoff wrote:
> On 08.07.19 08:28 , Dan Ports wrote:
>> On Sat, Jun 29, 2019 at 06:29:57PM +0200, joerg van den hoff wrote:
>>> would `port upgrade texlive' throw out an old texlive-latex-extra rather
>>> than upgrading (or ignoring) it? it shouldn't do
On 08.07.19 08:28 , Dan Ports wrote:
On Sat, Jun 29, 2019 at 06:29:57PM +0200, joerg van den hoff wrote:
would `port upgrade texlive' throw out an old texlive-latex-extra rather
than upgrading (or ignoring) it? it shouldn't do that but could it?
Yes, this can happen on occasion.
MacPorts
On Jul 4, 2019, at 12:12, Hongxia (Laura) Hao wrote:
> I am wondering if I need to install the whole xcode app before
> installing macports? Does that work if I only install the xcode
> command line tools?
As of right now, MacPorts assumes that Xcode exists, so our official
recommendation is
On Jul 3, 2019, at 10:41, Christoph Kukulies wrote:
> I ran in a Terminal the ImageMagick command:
>
> $ display image.jpg
>
> and got:
>
> display: delegate library support not built-in '' (X11) @
> error/display.c/DisplayImageCommand/1900.
When I Googled that error message, the
On Jul 6, 2019, at 11:27, rmgls wrote:
> trying to build samba4 i get these errors,
There are a few 6-year-old tickets open about the samba4 port, including a
build failure (for a different reason than the one you encountered) and a need
to update the port:
On Sat, Jun 29, 2019 at 06:29:57PM +0200, joerg van den hoff wrote:
> would `port upgrade texlive' throw out an old texlive-latex-extra rather
> than upgrading (or ignoring) it? it shouldn't do that but could it?
Yes, this can happen on occasion.
MacPorts doesn't have great support for enforcing
16 matches
Mail list logo
