I guess I've found a few packages that appear to work fine for ia64 despite being hardmasked due to not having the ia64 keyword. I wonder what's the normal method to progress from no keyword to full support?

Who ultimately needs to maintain that package for specific architectures, especially if they don't have that type of machine?_________________Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSDWhat am I supposed to be advocating?

Keywords are given when someone has tested that it works. If you have found a package with no keywords, tested it locally and it worked, file a bug on https://bugs.gentoo.org stating so._________________www.gentoo.org.au || #gentoo-au

How about the case of software that compiles/builds but does not seem to work perfectly?

Leave it keywordless?

I just tried rtorrent-0.7.2 / libtorrent-0.11.2 for ia64 - These sadly do not seem to work. Rtorrent builds cleanly, checksum the torrents just fine, know what files need to be downloaded, but sadly the network connections don't seem very clean - looks like I can initiate connections but not accept (?). It does apparently connect to the tracker and does get some peer lists. I was seeding a bit of a file too. Apparently this ebuild has some issues with 64-bit platforms as I get tons of unaligned accesses (which are fine just slow) - probably needs to be worked on by upstream.

I'll see if the newest version work better. Hopefully... _________________Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSDWhat am I supposed to be advocating?

I take that back. rtorrent actually does seem to work on one tracker (but seems quite slow on the gentoo tracker), but in any case, just a lot of spam from 64-bit coding issues...

hmm. I guess now it might actually be worth a keyword request - but the warning spam may make it somewhat ugly and difficult to use?_________________Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSDWhat am I supposed to be advocating?