-
-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add imap support #251
add imap support #251
Conversation
I can't do aarch64 debian testing (only alma & alpine) so I'm not sure if libpam will be required for aarch64 debian. I don't think so, though. And if it's not required, it's not worth including it imo. |
If you can create a debian aarch64 vhdx that I can upload to azure, I'll be able to test aarch64 debian in the future, by the way. Otherwise, it will have to wait until the 12c snapdragon releases - will finally get a laptop then. |
I'm writing a manually triggered testing actions here. It can specify different branches and repositories to test the extension combinations in the matrix of PHP8.0-8.2, Linux, macOS (using the official runner and local arm matrix). I am now separating the download file process to avoid repeated test failures due to accidental download errors, but I don’t know why only arm-macos cannot hit the cache and cannot get the output of the previous workflow. I'm working on it. FreeBSD is not a major platform, but it has good support for some common libraries. I currently reuse a lot of unix builds. However, imap is a relatively special library and may not be well suited to directly reusing unix compilation scripts for compilation. It may not be the main consideration for the current branch. |
--for-extensions is not working with it
Debian aarch64 is good. But macOS support is still bad:
|
Updates: I found that macOS is basically caused by the lack of system headers. Among them, |
But this causes a problem. I don't want to repeat so much repetitive content in the patch, and making the patch file seems to conflict with the existing patch. I wonder if we can directly fork |
Currently, it has been tested and runs well on Linux and macOS. Is it time to merge? BTW it would be better if you had checking code for imap extension. |
Checking code for imap extension? The default check with php --ri "imap" should work, right? |
In fact, it is a runtime test script, such as gd. If we don’t add it, and just use |
Yeah we don't need to write a test here I think. Just the default check is fine, since it won't show up if imap isn't supported. If MacOS works fine this is good to merge for me! |
this was considerably easier with the musl toolchains since it allows debian/ubuntu to build slx, which doesn't require libpam
closes #202
tests:
todo: (have no experience with bsd, don't own a mac or aarch64 hardware)