Task #2549
closedDo we have a support policy on architectures?
0%
Description
Somewhat related to https://pulp.plan.io/issues/2427. Is there an official policy around what arches pulp supports? We should probably test against these arches too.
Updated by semyers almost 8 years ago
As far as I know, we don't. My thinking is that things should generally work the same across architectures when we're using packages provided by fedora, but Fedora's own architecture support seems pretty limited, with "secondary" architectures (like ppc64) not receiving the same level of support as the "primary" arches: https://fedoraproject.org/wiki/Architectures
So I propose we effectively do the same, and only support arches listed as primary for fedora, and also be explicitly about what arches we support for rhel, which for el6 would probably be i686 & x86_64, and for el7 only x86_64.
Updated by bmbouter almost 8 years ago
Since we're not releasing builds for EL6 anymore, I think we can ignore a statement on it. For all other distros we support, (EL7+Fedora) I think going with x86_64 for now would be good. That is what we currently do (iirc).
Note that for pulp-agent we need to continue to build for other architectures. Broad compatibility is valuable there so I would recommend i386, i686, and x86_64. This should be easy because I believe everything required is a .noarch package. The thread referenced below talks some about that.
We discussed this some on the pulp-dev mailing list. See the thread titled "Dropping i386 Support" in the December archives
Updated by daviddavis about 7 years ago
- Status changed from ASSIGNED to NEW
- Assignee deleted (
daviddavis)
Updated by bmbouter over 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter over 5 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.