Pure python packages with unnecessary architecture restrictions

[Chandler Carruth]

Several packages within the overlay have only the 32-bit x86 architecture flag enabled (probably always the unstable "~x86" in an overlay), depsite being pure python packages. It would make more sense to use all of the viable python keywords, with "~" as appropriate to indicate unstable packages. Python 2.5 seems to be marked with the following keywords: "~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~sparc-fbsd ~x86 ~x86-fbsd".

[Mark Lee (malept)]

My policy is that I will keyword ~arch a package for any arch that someone verifies to me (via the bug tracker) that said builds, installs, and more or less works. I only have x86 machines, so most (if not all) of the packages are keyworded ~x86. Other people have indicated that various packages also work on amd64, so they're keyworded ~amd64.

If a package that you want does not have a keyword for your arch, verify that it builds/installs/runs on said arch and then file a bug here.

[Vadim Fint (mocksoul)]

Agree with Mark Lee, if anybody can verify packages in different architectures - do that :).