Summary: | dev-libs/tntnet, dev-libs/cxxtools architecture keywords | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Auke Booij (tulcod) <auke> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED NEEDINFO | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Auke Booij (tulcod)
2007-06-12 19:43:09 UTC
Please, only file keywording bugs about arches that you personally use and care about. Most arches will simply refuse to accept similar mass-keywording bugs filed just because something is allegedly "not architecture-specific". Hi, I'm the upstream. I have tested tntnet, cxxtools and tntdb on Kubuntu/x86 using gcc 4.1.2 20060928, Kubuntu/amd64 using gcc 4.1.2 20060928 and on AIX on ppc using xlc (the IBM-compiler). Others have reported tntnet working on FreeBSD using gcc (unknown version) and Solaris using SunStudio-compiler. There is no system-specific code in tntnet, cxxtools and tntdb, so there should be no problems regarding 32-bit/64-bit or little/big-endian or different compilers. (In reply to comment #2) I should be more clear, I guess? Most arches simply won't needlessly keyword stuff that none of their users is using. So, filing bugs saying that $ebuild should be keyworded everywhere just won't fly. If you are using this on some arch and want it keyworded there, then file a bug for that arch. Keywording for the sake of keywording is not useful. |