[Pkg-zsh-devel] Bug#632514: Bug#632514: zsh: architecture-dependent files in /usr/share

Axel Beckert abe at debian.org
Sun Jul 3 11:35:38 UTC 2011


severity 632514 minor
kthxbye

Hi Clint!

Clint Adams wrote:
> On Sun, Jul 03, 2011 at 03:30:46AM +0200, Axel Beckert wrote:
> > e) Make two arch-independent packages, one called zsh-zwc-le and only to
> >    be built on little endian architectures and one called zsh-zwc-be and
> >    only to be built on big endian architectures. (This hack is probably
> >    only policy-conforming if the files are installed in different
> >    directories afterwards, i.e. if zsh-zwc-le and zsh-zwc-be could be
> >    installed in parallel.)
> 
> .zwc files have a header which specifies the endianness of the file.

That's probably the one I cited from the vbindiff output. :-)

> If you want to create an _all.deb with the .zwc files, you would only
> need zsh-zwc.

That's indeed how I stumbled upon it.

Just to be sure: So this means I can use LE zwc files without problems
on BE architectures and vice versa?

> > f) Let upstream make the .zwc file format endianess-independent.
> 
> You could have it always generate BE no matter what architecture it's on.

Well, if BE and LE architectures can both cope with BE and LE zwc
files, I'd say, we just generate them whereever the package is first
build on and do not configure it explicitly (i.e. keep zwc file
generation like before).

In case that contrary to what we expect, this goes havoc, only the BE
archs like Sparc, PowerPC and MIPS will be affected as probably noone
of us will upload a package built on a BE architecture for an arch:any
package. :-)

Thanks for the information!

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5





More information about the Pkg-zsh-devel mailing list