On Thu, Jun 30, 2016 at 9:37 AM Stéphane Graber <firstname.lastname@example.org> wrote:
On Wed, Jun 29, 2016 at 09:33:24PM +0000, Robert Ancell wrote:
> It may be worth considering disabling i386 builds for individual packages
> to reduce the support costs. That way the core packages can build for i386
> and be used in IoT systems while the graphical application stacks can stop
> building for i386. There would be some challenges to negotiate overlap with
> the flavours (i.e. MATE might want their stack i386 and Unity not) and a
> practical way to do this (we don't want to have an Ubuntu version of the
> packages that come from Debian with only a change to the "Architecture"
> field in debian/control).
Doing so would prevent desktop users from installing binary 32bit
packages that rely on Ubuntu's multi-arch support.
I'm not sure how much of an issue this still is, given that a bunch of
them finally have 64bit builds now, but it may still be a problem for a
number of commercial software.
This would have to be done within the messaging of "i386 is no longer supported on Ubuntu desktop after 16.04" meaning we would expect that third party i386 software would no longer work. Of course, they should provide i386 snaps with all the libraries installed if they want to keep shipping in that form...