Thursday, 13 February 2014

Re: remove i386 from foreign arch on server install?

On 13 February 2014 11:24, Scott Moser <[email protected]> wrote:
> Hey all,
> I just did an ISO server install of trusty server, and I end up with
> 'i386' in the output of:
> $ dpkg --print-foreign-architectures
> i386
>
> I really wish we'd have done it earlier, but I really think that most of
> the time this is just a waste of network traffic on 'apt-get update' on a
> server. If people want i386 packages on amd64, its trivial for them to
> re-enable it.
>
> What do people think about removing this?
> Does anyone have a use case where this is important, and is not easily
> worked around just by doing:
> sudo dpkg --add-architecture i386
>

I'd like to see i386 to still be enabled in dpkg by default on amd64.
However, I do agree that it is undesirable side-effect of downloading
apt-metadata for packages one might not install on a given machine.
Disabling i386 on dpkg level, does not bring us closer to be able
eventually in the future more amd64 from primary mirrors, to ports
mirrors.

How about, starting to arch qualify sources lists?

Cause what I think you really want on the server is this:
deb [arch=amd64] http://archive.ubuntu.com/ubuntu trusty main universe
multiverse restricted
deb-src http://archive.ubuntu.com/ubuntu trusty main universe
multiverse restricted

On the desktop (one can also use [arch=i386,amd64] instead of doing
one line per arch):
deb [arch=i386] http://archive.ubuntu.com/ubuntu trusty main universe
multiverse restricted
deb [arch=amd64] http://archive.ubuntu.com/ubuntu trusty main universe
multiverse restricted
deb-src http://archive.ubuntu.com/ubuntu trusty main universe
multiverse restricted

On a developer machine:
deb [arch=i386,amd64] http://archive.ubuntu.com/ubuntu trusty main
universe multiverse restricted
deb [arch=armhf] http://ports.ubuntu.com/ubuntu-ports trusty main
universe multiverse restricted
deb-src http://archive.ubuntu.com/ubuntu trusty main universe
multiverse restricted

The case for multiarch by default (in dpkg-only) on the server is easy
trail for sys-admin to find: installing _i386, argh apt says missing
packages, check apt sources, AHA i need i386 repository added. Boom
everything works. vs zero hints that both architecture and
repositories need to be enabled.
The case for multiarch by default (both dpkg and apt-sources) on the
desktop is: Steam, Skype, Wine, etc.
The case for multiarch by default (armhf is self configured in sources
- undecided if it should be enabled in dpkg by default) on the
developer machine: is cross-compilation to mobile/embedded, and/or
multilib compilation to 32-bit.

--
Regards,

Dimitri.

--
ubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel