On Oct 18, 2020, at 20:38, Zhenfu Shi wrote:
> On Oct 18, 2020, at 21:33, Ryan Schmidt wrote:
>
>> It gets through, but shows your gmail address as the from address. I don't
>> think gmail supports customizing the from address anymore either.
>
> Yeah it got t
On Oct 19, 2020, at 14:10, Christopher Chavez wrote:
> So far the versions for Python have been able to compact into two-digit
> strings: e.g. 36 37 38 39. Is the compacted version number for next year's
> Python 3.10 going to be "310"?
>
> If so, there is code in portfiles which requires adjus
On Oct 24, 2020, at 11:46, Ken Cunningham wrote:
> So instead of this method, I will look into running lsearch on *.env, and see
> if I can sort out how to add some entries if something is already there.
MacPorts base makes this easier for specific variables by offering MacPorts
variables t
On Oct 24, 2020, at 19:51, Ken Cunningham wrote:
> On Oct 24, 2020, at 3:36 PM, Ryan Schmidt wrote:
>
>> On Oct 24, 2020, at 11:46, Ken Cunningham wrote:
>>
>>> So instead of this method, I will look into running lsearch on *.env, and
>>> see if I can
On Oct 24, 2020, at 21:51, Joshua Root wrote:
> On 2020-10-25 03:46 , Ken Cunningham wrote:
>> Do you think this:
>>
>> configure.env-append"DYLD_LIBRARY_PATH=${prefix}/lib/lilbgcc"
>> configure.env-append“DYLD_LIBRARY_PATH=${workpath}/build”
>>
>> should “just work" to set bo
On Oct 27, 2020, at 07:20, Steven Smith wrote:
> Apple’s legacy binary protocol is deprecated as of November 2020:
> https://developer.apple.com/news/?id=11042019a&1572897862
>
> The PR https://github.com/macports/macports-ports/pull/8719 addresses the new
> protocol.
>
> Would someone plea
On Oct 30, 2020, at 09:48, René J.V. Bertin wrote:
> why doesn't `default_variant` notice that it's setting a variant that
> conflicts with a variant set by the user?
I guess it just wasn't written to take that into account. Modifying it to add
that enhancement might be reasonable, but we wo
On Nov 2, 2020, at 13:14, Mojca Miklavec wrote:
> If I understand correctly, we'll soon be unable to run any builds on
> Travis unless we pay for it (they are gradually moving existing
> customers to the new billing plan, so it's just a matter of time):
>https://blog.travis-ci.com/2020-11-0
On Nov 3, 2020, at 04:52, Vincent Habchi wrote:
> Atlas, the software meant to provide scientific computing tools with a
> high-performance assembly-based library has, IMHO, reached its end of life.
>
> My case is this:
>
> • Last developer (unstable) release is more than two years old;
> • La
On Nov 5, 2020, at 18:43, Fred Wright wrote:
> On Thu, 5 Nov 2020, Ryan Schmidt wrote:
>
>> DSDP
>> R
>> esmf
>> gr-specest
>> itpp
>> levmar
>> lua-numlua
>> nco
>> psfex
>> py-numpy
>> py-scipy
>> scamp
>
On Nov 8, 2020, at 11:12, Ken Cunningham wrote:
> new install on a catalina system, then run port selfupdate, and then port
> diagnose:
>
> % sudo port -v diagnose
> Error: currently installed version of Xcode, 12.1, is not supported by
> MacPorts. For your currently installed system,
On Nov 10, 2020, at 16:02, Ruben Di Battista wrote:
> Can any of you please review this:
> https://github.com/macports/macports-ports/pull/8836 and merge it? The VTK
> port’s been broken for a while. I think it might be worth it to land this for
> the new port and wait for possible tickets on `
Apple has announced that macOS 11 Big Sur will be released tomorrow, November
12, 2020, and that Apple Silicon machines will be available starting November
17.
We will need a new release of MacPorts (2.6.4 or 2.7.0) to support Apple
Silicon. What we have in git master is probably most of the wa
On Nov 11, 2020, at 10:24, Ryan Schmidt wrote:
> Are there any other fixes that need to go into the next release that haven't
> already been committed? Any PRs not yet merged that we want?
It would be good to fix the compiler selection for thread local storage with
C+
On Sep 22, 2020, at 05:58, Ryan Schmidt wrote:
> It would be nice if we could easily switch our precompiled archives from
> bzip2-compressed tarballs (tbz2) to better compression methods as they become
> available. For example, xz-compressed tarballs (txz) would be better today.
&g
On Nov 11, 2020, at 14:05, Joshua Root wrote:
> On 2020-11-12 04:25 , Ryan Schmidt wrote:
>> One problem is that the archive stays on the user's computer and MacPorts
>> needs to know how to decompress it when the port is activated.
> You can already install diffe
On Nov 13, 2020, at 18:34, Nils Breunese wrote:
> Nils Breunese wrote:
>
>> Every time MacPorts tries to install the p5.28-locale-gettext port on my Big
>> Sur 11.0.1 machine, the OS crashes and the Problem Reporter shows the crash
>> report below. Does installing this port work for others o
On Nov 14, 2020, at 09:09, Jan Trtík wrote:
> do you have, by any chance, Little Snitch installed on your computer?
> I had same problem and it went away as soon as I removed it… I am still
> trying to find out what exactly does trigger this issue, but this at least
> allowed me to migrate M
On Nov 14, 2020, at 11:17, Nils Breunese wrote:
> Ryan Schmidt wrote:
>
>> Sounds like maybe another consequence of the massive number of processes
>> that MacPorts starts when trying to determine which of the hundreds of perl
>> master_sites is closest t
On Nov 14, 2020, at 13:58, Nils Breunese wrote:
> Ryan Schmidt wrote:
>
>> You could edit the source code to change 50 to a smaller number and try
>> again. To ensure that your test is not influenced by previously cached
>> entries, delete /opt/local/var/macports
On Nov 16, 2020, at 20:23, Christopher Jones wrote:
>> On 17 Nov 2020, at 2:18 am, Zero King wrote:
>>
>> On Tue, Nov 17, 2020 at 02:09:11AM +, Christopher Jones wrote:
>>> Hi,
>>> Is anyone else having problems installing tarballs from the new Darwin20
>>> builedbot ?
>>
>> Yes, see htt
On Nov 17, 2020, at 21:37, Clemens Lang wrote:
> - Configure your mail client to send mail from your @macports.org
> address as documented at
> https://smtpselfservice.macports.org/settings.
Could you provide more guidance on how to do this in Apple's Mail.app on macOS,
iOS, iPadOS?
Do w
On Nov 17, 2020, at 23:30, Clemens Lang wrote:
> Hi Ryan,
>
> On Tue, Nov 17, 2020 at 10:17:29PM -0600, Ryan Schmidt wrote:
>> Could you provide more guidance on how to do this in Apple's Mail.app
>> on macOS, iOS, iPadOS?
>
> I don't use Mail.app, so I h
On Nov 18, 2020, at 00:10, Ryan Schmidt wrote:
>
> On Nov 18, 2020, at 00:05, Clemens Lang wrote:
>
>> I believe you can choose to store sent mail in a different account's
>> IMAP sent folder in Preferences > Accounts > Mailbox Behaviors.
>
> Right, bu
On Nov 18, 2020, at 20:00, Ryan Schmidt wrote:
>
> But, if this email shows up, then at least hopefully the SMTP settings are
> working.
No, based on the headers, apparently it still uses my main SMTP server, even
though I have selected the MacPorts SMTP server for this account.
On Nov 18, 2020, at 20:03, Ryan Schmidt wrote:
> On Nov 18, 2020, at 20:00, Ryan Schmidt wrote:
>>
>> But, if this email shows up, then at least hopefully the SMTP settings are
>> working.
>
> No, based on the headers, apparently it still uses my main SMTP se
Based on the fact that Apple has released a beta of macOS Big Sur 11.1 already,
we can now see that Big Sur should be referred to as version 11, not 11.0 (and
it would be reasonable to expect that next year's macOS will be version 12).
If you are fixing any ports that had been coded to assume th
On Nov 18, 2020, at 20:28, Saagar Jha wrote:
> On Nov 18, 2020, at 18:12, Ryan Schmidt wrote:
>>
>> Based on the fact that Apple has released a beta of macOS Big Sur 11.1
>> already, we can now see that Big Sur should be referred to as version 11,
>> not 11.0 (an
On Nov 18, 2020, at 21:04, Chris Jones wrote:
> On 19 Nov 2020, at 2:31 am, Ryan Schmidt wrote:
>
>>> On Nov 18, 2020, at 20:28, Saagar Jha wrote:
>>>
>>>> On Nov 18, 2020, at 18:12, Ryan Schmidt wrote:
>>>>
>>>> Based on t
On Nov 19, 2020, at 20:55, Aaron Madlon-Kay wrote:
> I have a port (Sequel-Ace) that builds with the SDK in Xcode, e.g.
>
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.0.sdk
>
> ...but not with the CLI SDK, e.g.
>
> /Library/Developer/CommandL
On Nov 20, 2020, at 01:05, Aaron Madlon-Kay wrote:
> (Replying to list as well this time)
>
>>> Is there a way to force use of the Xcode SDK?
>>
>> use_xcode yes
>
> Sorry, I should have mentioned that I tried that, but the result was
> that it still used the CLI SDK:
>
> SDKROOT='/Library/
On Nov 20, 2020, at 16:30, Aaron Madlon-Kay wrote:
> On Fri, Nov 20, 2020 at 11:47 PM Joshua Root wrote:
>> Unfortunately it isn't really. The result of not using an SDK matching
>> your OS version is that autoconf (and cmake etc.) detects functions that
>> aren't available at runtime, causing
On Nov 20, 2020, at 09:54, Clemens Lang wrote:
> I'm very-well aware of this problem. However, when `use_xcode` is set, I
> think we must prefer an Xcode SDK with the required tools for GUI stuff,
> even if it isn't the exact version and a CLT SDK with the expected
> version is available.
What
On Nov 17, 2020, at 21:37, Clemens Lang wrote:
> On Tue, Nov 17, 2020 at 04:35:50PM +0100, Clemens Lang wrote:
>> As a consequence, I will be setting up an SMTP submission service on
>> our server. I will also provide a self-service to set your SMTP
>> password that will leverage GitHub OAuth2
On Nov 22, 2020, at 15:56, Clemens Lang wrote:
>
> On Fri, Nov 20, 2020 at 04:54:28PM -0600, Ryan Schmidt wrote:
>> On Nov 17, 2020, at 21:37, Clemens Lang wrote:
>>
>> I'm not able to send mail through this server today. Mail.app's
>> connection doctor
On Nov 23, 2020, at 13:08, Clemens Lang wrote:
>
> Hi Ryan,
>
> On Sun, Nov 22, 2020 at 09:19:43PM -0600, Ryan Schmidt wrote:
>> I tried just now. (2020-11-23 03:14 UTC) It failed. The Mail.app sheet
>> said:
>>
>> [...]
>>
>> There is a but
Heads up! install_name_tool in Xcode 12.2 -- the version we are using for Big
Sur -- has a bug that could affect ports. If you give install_name_tool a path
to a symlink to a library, you might expect it to modify the library, and
that's what it did in previous versions of Xcode. But in Xcode 12
On Nov 24, 2020, at 16:15, Clemens Lang wrote:
> This will become a significant problem with the release of Big Sur,
> since Apple has made -Wimplicit-function-declaration an error by default
> due to details of the calling convention on Apple Silicon.
Thanks Clemens. I've been meaning to writ
On Nov 24, 2020, at 11:41, Ken Cunningham wrote:
> presumably they have switched to using “openat” or similar and have not used
> the proper flags somehow.
No idea, though I know that they did modify install_name_tool so that it would
preserve ad hoc codesigning, and my guess would be that this
> On Nov 27, 2020, at 10:24, Zero King wrote:
>
> If we can install .pkgs from the command line and
> skip the initial sync (in the postflight script), we could throw it away
> and just use official pkg installers.
Yes I would like that. I spent some time awhile back rewriting the installer
w
On Dec 1, 2020, at 00:07, Ken Cunningham wrote:
> another reasonably simple option would be to have a manual step, and copy
> what happens with apple-gcc42 +bootstrap.
>
>
> We make up a non-TLS variant of libcxx, call it libcxx +bootstrap, and
> default to installing that if there is nothi
On Dec 6, 2020, at 14:19, Mark Anderson wrote:
> I get a lot of these:
>
> ---> Scanning binaries for linking errors
> Could not open /usr/lib/libz.1.dylib: Shared cache only (referenced from
> /Applications/MacPorts/iTerm2.app/Contents/Frameworks/NMSSH.framework/Versions/A/NMSSH)
This comm
On Dec 6, 2020, at 15:16, Mark Anderson wrote:
> Is there a good way to get 10.6 - 10.16 installed in Parallels — I really
> don't want to download all of them from the app store, if that's even
> possible.
Why don't you want to download from Apple? That's the only official place to
get mac
On Dec 6, 2020, at 15:54, Mojca Miklavec wrote:
> On Sun, 6 Dec 2020 at 22:37, Christopher Nielsen wrote:
>>> On 2020-12-06-S, at 16:16, Mark Anderson wrote:
>>>
>>> Is there a good way to get 10.6 - 10.16 installed in Parallels — I really
>>> don't want to download all of them from the app s
On Dec 6, 2020, at 20:16, Christopher Nielsen wrote:
> On 2020-12-06-S, at 20:15, Ryan Schmidt wrote:
>
>> As you know the 2009 Xserves I use to run the MacPorts Buildbot system run
>> VMware ESXi 6.0.0 and are running VMs from Snow Leopard through Big Sur.
>> Leo
On Dec 6, 2020, at 20:21, Michael wrote:
> Ok, lets say I wanted to use a 2014 laptop running 10.9.5 as the host --
> which VM would let me run a 10.12 and a 10.14 guest?
>
> Bonus points if it can run a 10.7 (lion) guest.
Well your options are VMware Fusion, Parallels Desktop and VirtualBo
On Dec 16, 2020, at 21:11, Ken Cunningham wrote:
> octave has like 117 deps
>
> does anyone have a script that will do this? I have just done it by hand
> before, but that’s too much gruntwork if there’s an easier way.
I believe some people have attempted to write such scripts, but such scri
On Dec 11, 2020, at 12:20, Christopher Nielsen wrote:
> Is it possible to easily override the ccache directory via command-line, with
> the goal of maintaining separate caches per port?
>
> I did some quick digging through the MacPorts TCL files, and didn’t see
> support for such an override
On Dec 17, 2020, at 08:17, Aaron Madlon-Kay wrote:
> A port I maintain, Sequel-Ace, has recently switched from including a
> dependency with CocoaPods (which vendors all dependency code alongside the
> main project in the same repo) to Swift Package Manager (which fetches at
> build time):
>
On Dec 17, 2020, at 09:29, Ken Cunningham wrote:
> we are not likely to win this...we accept the package manager when it cones
> to ghc/stack,
We don't really. Having an updated working ghc/stack for some systems was
better than not having it for any systems, but it sucks and needs to be fix
On Dec 17, 2020, at 10:23, Michael Dickens wrote:
> The best solution I've been able to come up with is to make new boostXYZ
> ports that are installable in parallel: boost169 already exists, as noted; I
> don't have it installed yet, but it's on my list to do so, to try to figure
> out the
On Dec 18, 2020, at 11:44, Joshua Root wrote:
> I don't know if the 11.1 SDK
> actually added new APIs, but if so, building against it will result in
> binaries that may not run on an 11.0 system.
I wouldn't worry about differences between different 11.x SDKs. I don't see
this as being different
Re-sending to correct list address. Remember to use list addresses at
lists.macports.org, not the old list address that we used prior to 2017.
On Dec 26, 2020, at 15:52, Bjarne D Mathiesen wrote:
> When upgrading from php74
>
> $=> cat php.bash
> #!/opt/local/bin/bash
>
> phpOld=${1:-74}
> php
On Dec 30, 2020, at 10:30, wowfunha...@gmail.com wrote:
>> You are one of our strongest proponents of keeping software working on older
>> systems. A build system that forces fetching from a specific upstream server
>> reduces our ability to build on older systems, since that specific server
On Dec 31, 2020, at 10:56, Ken Cunningham wrote:
> So I will make another push for this, before we get hundreds of ports built
> with incorrect burned-in SDKs that make a total mess for us to manage.
>
>
> What is different now is that almost all current configure software does a
> test-compil
On Dec 31, 2020, at 15:54, Ken Cunningham wrote:
> On Dec 31, 2020, at 1:51 PM, Ryan Schmidt wrote:
>
>> On Dec 31, 2020, at 10:56, Ken Cunningham wrote:
>>
>>> So I will make another push for this, before we get hundreds of ports built
>>> with incorr
On Jan 5, 2021, at 20:43, Herby G wrote:
> For the last few days, CI runs in Github under both Github Actions & Azure
> Pipelines have been failing because port is rebuilding every dependency for a
> given port from scratch for some reason.
>
> This is causing CI builds to take hours to buil
On Jan 11, 2021, at 19:39, Craig Treleaven wrote:
> My MythTV ports depend heavily on Qt but I’m not up to speed on that
> project’s plans wrt the new Apple-silicon (ASi) Macs. AIUI, our current Qt5
> port is X86_64 only. Is or will Qt5 be compatible with ASi? Do we need to
> port Qt6 to
On Jan 11, 2021, at 19:38, Craig Treleaven wrote:
> A user with a new Apple Silicon-based Mac had a go at building mythtv.28. It
> failed thusly:
>
> ---> Computing dependencies for mythtv.28
> Error: Cannot install mythtv-core.28 for the arch 'x86_64' because
> Error: its dependency logrot
On Jan 12, 2021, at 10:51, Christopher Nielsen wrote:
> A few of our ports are failing on the build infrastructure, for target Big
> Sur x86_64. And one of the culprits is portmidi, which causes downstream
> ports to fail during the install-dependencies phase because "Dependency
> 'portmidi' wi
On Jan 13, 2021, at 11:19, Christopher Nielsen wrote:
> For anyone who’s interested, our 10.14 builder appears to be offline.
>
> Ticket submitted yesterday:
> https://trac.macports.org/ticket/62047
>
Back online now.
On Jan 1, 2021, at 11:38, Ken Cunningham wrote:
>> A similar problem is when build systems save the compiler that was used into
>> files that get installed and then try to use that compiler later to build
>> other modules; perl does this. And this causes problems like
>> https://trac.macport
On Jan 15, 2021, at 20:07, Steven Smith wrote:
> I am unable to build grpc on a specific machine because of some Xcode error:
>
>> make[2]: *** No rule to make target
>> `/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Framewo
On Jan 17, 2021, at 14:16, Steven Smith wrote:
> This flag is being passed to cmake in the MacPorts build. Is this the issue?
>
>> -DCMAKE_OSX_SYSROOT="/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk"
>
> It doesn’t appear consistent with the error:
>
>> make[2]: *** No rule to make
On Jan 17, 2021, at 10:49, Ken Cunningham wrote:
>> This kind of problem is the reason why I keep our Buildbot machines on a
>> version of Xcode and command line tools that contains the SDK version
>> matching the OS version.
> The downside is all the newer software that should but won’t buil
On Jan 18, 2021, at 08:35, Craig Treleaven wrote:
>> The correct spelling is CoreMIDI, not CoreMidi. You get away with it on a
>> case-insensitive filesystem.
>
> Thanks. I’ve pushed a commit that I hope fixes the CoreMIDI issue. Although
> the buildbots don’t seem to be picking it up.
Mo
On Jan 18, 2021, at 21:23, Craig Treleaven wrote:
> On Jan 18, 2021, at 10:01 PM, Ryan Schmidt wrote:
>
>> On Jan 18, 2021, at 08:35, Craig Treleaven wrote:
>>
>>>> The correct spelling is CoreMIDI, not CoreMidi. You get away with it on a
>>>> ca
On Jan 19, 2021, at 14:22, Christopher Nielsen wrote:
> This isn’t urgent - I was simply interested in checking the build backlog -
> but can’t get a response from build.macports.org.
>
> Earlier I was seeing a “Bad Gateway” message via web browser, now it’s simply
> timing out with a blank pag
On Jan 19, 2021, at 18:17, Ryan Schmidt wrote:
> On Jan 19, 2021, at 14:22, Christopher Nielsen wrote:
>
>> This isn’t urgent - I was simply interested in checking the build backlog -
>> but can’t get a response from build.macports.org.
>>
>> Earlier I was seei
On Jan 20, 2021, at 09:47, filhol wrote:
> I am new at this mailing list and I hope my question is not out of scope.
Welcome!
> An X11 based application can easily notarised, but is it possible to publish
> to it to the Mac App Store ?
> If someone already succeeded what is the recipe ?
> Fo
On Jan 20, 2021, at 18:01, filhol wrote:
> On 21 Jan 2021, at 00:53, Ryan Schmidt wrote:
>
>> On Jan 20, 2021, at 09:47, filhol wrote:
>>
>>> I am new at this mailing list and I hope my question is not out of scope.
>>
>> Welcome!
>>
>>>
On Jan 20, 2021, at 18:37, filhol wrote:
> On 21 Jan 2021, at 01:19, Ryan Schmidt wrote:
>
>> Another worthwhile consideration for you or anyone else thinking of
>> attempting this is whether it is appropriate to bundle an X11 server with
>> your app. What if the use
On Jan 21, 2021, at 02:06, Bjarne D Mathiesen wrote:
> php80-imagick can be installed directly from git :
> ( https://github.com/Imagick/imagick/issues/358 )
Yes, but if you actually read that issue, you'll find that the author is not
ready to declare that code as the PHP 8-compatible release ye
On Jan 21, 2021, at 02:04, Bjarne D Mathiesen wrote:
> Ken Cunningham wrote:
>> It builds on 10.4 to 10.14 at least; dunno about 10.15, although gcc5
>> seems to build there. Haven't tried.
>
> Doesn't work on my 10.15
Normally it would be helpful to provide more information. In this case we c
On Jan 24, 2021, at 17:52, Ruben Di Battista wrote:
> I think that one of the selling points of Macports, at least for me, is
> providing ports for legacy systems. So on the ports I maintain, I try to fix
> build issues on old systems. The problem is that it’s very difficult to do it
> since
On Jan 25, 2021, at 01:55, Joshua Root wrote:
> On 2021-1-25 18:48 , Andrew Janke wrote:
>> How do you download the installers for Big Sur and for older versions of
>> macOS? I've always had to go through the App Store to download installers,
>> and what it makes available for me is dependent
On Jan 25, 2021, at 10:03, Andrew Janke wrote:
> On 1/25/21 10:31 AM, Ryan Schmidt wrote:
>> On Jan 25, 2021, at 01:55, Joshua Root wrote:
>>
>>> On 2021-1-25 18:48 , Andrew Janke wrote:
>>>> How do you download the installers for Big Sur and for older version
On Jan 25, 2021, at 10:02, Ruben Di Battista wrote:
> If I configured a server I own to run CI jobs for old systems (I was thinking
> about using a custom Gitlab runner libvirt
> https://docs.gitlab.com/runner/executors/custom_examples/libvirt.html for
> that and maybe), it's gonna be someth
On Jan 25, 2021, at 11:37, Clemens Lang wrote:
> I personally wouldn't have a problem with optional CI steps running on
> other people's machines, as long as that's for pull requests and we
> don't use the results anyhere but to post status information to GitHub.
There would be an advantage to
On Jan 27, 2021, at 06:32, Mojca Miklavec wrote:
> Maybe GitLab runner isn't able to run on the oldest macOS that we
> support, but if you run it on the host just to fire up a VM, that
> might be ok.
>
> I see that GitLab supports CI on top of GitHub repository:
>
> https://docs.gitlab.com/ee
On Feb 2, 2021, at 18:27, Craig Treleaven wrote:
> In the dav1d PR, CI didn’t produce results for the older OS versions. I
> thought the CI system was just being grumpy.
Our CI system uses publicly available build infrastructure from GitHub, which
only offers build machines running current
On Feb 2, 2021, at 11:18, Ken Cunningham wrote:
> One port needed +universal has some tricks in it, and requires
> "merger_must_run_binaries". That port cannot be built universal on an Intel
> system (which can't run arm64) but can be built universal on an arm64 system
> (which can run Intel
On Feb 1, 2021, at 09:49, Christopher Nielsen wrote:
> Given how long the various openmpi-* subports take to build, it would be
> beneficial to publish binaries for our users.
>
> This is currently disabled in the Portfile, with a brief mention that it’s
> due to ‘hwloc’... and the tight coupli
On Feb 3, 2021, at 01:12, Ken Cunningham wrote:
>> But if "his system will never see that port could be universal" then how
>> could he "download and install that port +universal" in the first place?
>
> that is the crux of it, indeed.
>
> Should our poor soul, who cannot build the port +unive
On Feb 3, 2021, at 01:29, Ken Cunningham wrote:
> On Feb 2, 2021, at 11:22 PM, Ryan Schmidt wrote:
>
>> I consider the buildbot a "nice to have". It makes life easier by
>> precompiling things but it is not essential. When something is not available
>> precom
On Feb 3, 2021, at 03:29, Eric Borisch wrote:
> This seems off.
>
> Hwloc’s own page talks about the availability of pre-compiled packages, and
> its demos focus on determining what threads to bind to (on OSes where
> explicit binding is possible; last I checked it wasn’t on OSX) if you want
On Feb 5, 2021, at 13:00, Ken Cunningham wrote:
> With no plan, we’ll just keep getting more and more of these.
I'm not aware of a huge influx of these, but I'm also not really paying
attention to the PR queue. And I'm not intending to get drawn into this
discussion of binary ports again.
On Feb 4, 2021, at 11:26, Ken Cunningham wrote:
> wait, I could have missed the issue...if meson is now adding a default
> argument to all checks that means it can never build anything with the
> default compilers on <10.10, that would be something we should consider
> fixing in meson, even
On Feb 6, 2021, at 02:28, Ken Cunningham wrote:
>>> This kind of port just repackages the DMG into many tgz archives.
>>>
>>> It’s wasteful. People want them.
>>>
>>> What we should have instead of this is some kinda tech that
>>>
>>> 1. downloads the DMG
>>> 2. installs the app
>>> 3. records
On Feb 6, 2021, at 02:14, Ken Cunningham wrote:
> On Feb 5, 2021, at 10:04 PM, Ryan Schmidt wrote:
>
>> That sounds like what Craig is saying: that meson is now adding a compiler
>> flag that old compilers don't understand. Meson should check whether a
>> compi
On Feb 6, 2021, at 04:15, Ken Cunningham wrote:
> try the sagemath one if you like. It's all set, for a newish system at
> present:
>
> https://github.com/kencu/myports/blob/master/binary/sagemath-binary/Portfile
>
> It is a stress test, for sure -- and I fully admit you may know simple twea
On Feb 6, 2021, at 09:17, Ken Cunningham wrote:
> those are the small things.
>
> I stopped when the broad strokes, as it is now, were a unworkable disaster.
I don't understand which aspects are an unworkable disaster. As I said, based
on what you've said so far, it seems like everything sho
On Feb 6, 2021, at 11:55, Lothar Haeger wrote:
> The latest version of FileZilla fails to build on my Catalina system and the
> developer states, it requires the latest BigSur SDK to compile (though the
> final binary should be running on macOS 10.11 and newer):
>
> → https://trac.file
On Feb 7, 2021, at 09:59, Ken Cunningham wrote:
> On Feb 7, 2021, at 03:17, Clemens Lang wrote:
>
>> Hi Ken,
>>
>>> On Sat, Feb 06, 2021 at 11:35:58PM -0800, Ken Cunningham wrote:
>>> although I was concerned about getting this pattern right before we
>>> had too many of these to fix, it does se
On Jan 31, 2021, at 11:05, harens wrote:
> I completely agree that Homebrew is currently winning at publicity.
What should the MacPorts community be doing do publicize MacPorts better?
> I think vocalising the points of Saagar Jha’s article Thoughts on macOS
> Package Managers would be very
On Feb 11, 2021, at 04:21, Christopher Jones wrote:
> I am seeing some large builds fail due to drive space issues
>
> https://build.macports.org/builders/ports-11_x86_64-builder/builds/21466/steps/install-port/logs/stdio
> error:
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefa
On Feb 11, 2021, at 18:45, Ryan Schmidt wrote:
> On Feb 11, 2021, at 04:21, Christopher Jones wrote:
>
>> I am seeing some large builds fail due to drive space issues
>>
>> https://build.macports.org/builders/ports-11_x86_64-builder/builds/21466/steps/install-
On Feb 12, 2021, at 20:57, Ruben Di Battista wrote:
> Hello, I was exploring a bit how to build the CI system for old platforms and
> the first step was to virtualize old macOS version. I'd like to do it using
> KVM. I was following this: https://github.com/kholia/OSX-KVM, but trying to
> insta
On Feb 11, 2021, at 19:19, Ryan Schmidt wrote:
> On Feb 11, 2021, at 18:45, Ryan Schmidt wrote:
>
>> On Feb 11, 2021, at 04:21, Christopher Jones wrote:
>>
>>> I am seeing some large builds fail due to drive space issues
>>>
>>> https://build.
On Feb 13, 2021, at 04:21, Chris Jones wrote:
> On 13 Feb 2021, at 9:06 am, Ryan Schmidt wrote:
>
>> Apple helpfully recreated the CoreSimulator directory again today. I'm not
>> going to delete it again unless we have a plan for how to prevent it from
>&
701 - 800 of 1750 matches
Mail list logo
