-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
Enhancement (docker): Add more archs #1321
Enhancement (docker): Add more archs #1321
Conversation
Should we really add ARMv6 and ARMv7? |
Agreed. They are taking super long to build, over an hour. So, only |
bb0d349
to
c4b0b78
Compare
worth adding |
When people start using 64bit mainframes and docker. They will also probably ask to support MAILBOX-REFERRALS (RFC 2193, 5258) 😆
|
don't really know what that means 😕 you mean that's only supported on |
linux/arm64
arch0ab08f3
to
4f45a72
Compare
IMAP can be setup to have "remote" mailboxes. With |
i see, shouldn't this be a IMAP protocol specific implementation? for it to be specific to an arch is strange. |
It is IMAP protocol specific. But i wonder if we should support 390x |
yeah. but so long as the builds / tests succeed, it is assumed that 390x should work just as any arch would. It's not very used much in the wild anyway 🥲 |
guess we could drop it? your take i guess 😄 |
Then skip it. Arm64 will be enough then. |
4f45a72
to
5265883
Compare
I will keep in mind to drop |
|
Let me rebase |
5265883
to
33558bf
Compare
where are you seeing the yaml error? |
at docker build |
see it, second |
7c205ad
to
7f6833f
Compare
39 mins for cacheless builds, guess that's fine? but there's docker caching in the CI, so if it hits the cache, it will be much faster. Which, should be most of the time. |
The build succeeded, see leojonathanoh#2.