Although a 64-bit flash is a very nice thing to have, we shouldn't just install it without warning. The common setup on amd64 is having a 32-Bit firefox with 32-bit java and 32-bit flash. Installing a 64-bit flash on top of this just breaks everything. I'm not sure how to resolve this, maybe the new version should be hardmasked at least until java 1.6.0.12 is available, because having a 32bit browser with only a working java, right next to a 64bit browser with only a working flash is definitely not feasible setup. Reproducible: Always Steps to Reproduce: on ~amd64: emerge netscape-flash
Maybe some elog message would be useful for the 64-bit flash ebuilds. Anyway, if you want to stick with 32-bit flash, try this line in /etc/portage/package.keywords: net-www/netscape-flash -~amd64 ~x86 (note the "-" as prefix of ~amd64)
Yes, this does beg the question of what to do about people who run both the 64-bin and 32-bit firefox. Perhaps I should slot the 64-bit flash differently so they can be installed simultaneously.
I was using the precompiled 32bit firefox just for flash's sake, so as soon as the 64bit java nsplugin is ready, I'll be switching to 64bit firefox, because it also saves me some audio lib mess in /usr/local. I think having a 64bit java and flash eliminates the need for a precompiled firefox in most setups. But, yeah, we might want to have two different ebuilds or slots, just like we do with firefox and firefox-bin for those people who still need both.
I suppose I could also just have a IUSE="multilib" which, for amd64 folks, would end up installing both versions. This will be a bit ugly before the version number matches for both versions, but I hope once the 64-bit one is actually released, both versions will match. Even then, this may not be the appropriate solution... time to do some deep thinking. In the mean time I have added an elog warning to the alpha version.
(In reply to comment #4) > I suppose I could also just have a IUSE="multilib" which, for amd64 folks, > would end up installing both versions. This will be a bit ugly before the > version number matches for both versions, but I hope once the 64-bit one is > actually released, both versions will match. Even then, this may not be the > appropriate solution... time to do some deep thinking. > > In the mean time I have added an elog warning to the alpha version. > Any reason not to split to a separate ebuild e.g. net-www/netscape-flash64?
(In reply to comment #5) > Any reason not to split to a separate ebuild e.g. net-www/netscape-flash64? That is certainly an option I'm considering. But it seems odd to have 2 packages for a single piece of software on 2 different architectures - Normally this is what KEYWORDS is for :)
well, with having two ebuilds, at least the oddness will be in sync with firefox...
As long as we are stuck with 32bit java and pdf plugins, where will be times that firefox-bin is the only option and not having flash is a pain, especially since firefox64 and firefox-bin cannot run at the same time. Obviously 64bit plugins for everything is preferrable.
(In reply to comment #8) > As long as we are stuck with 32bit java and pdf plugins, where will be times > that firefox-bin is the only option and not having flash is a pain, especially > since firefox64 and firefox-bin cannot run at the same time. Obviously 64bit > plugins for everything is preferrable. Well, you can use nspluginwrapper with the acroread plugin in a 64-bit browser.(though I personally just use epdfview - much faster to load) And 64-bit java is on the way. Apparently sun-jre-bin/1.6.0.12 will have a 64-bit javaws and plugin. also, the experimental icedtea6 in the experimental 'java-overlay' will build a 64-bit plugin which works for most applets most of the time. But once the 64-bit flash plugin is actually released (and more specifically has a 32-bit release with the same versioning), I will make it possible to install the 32-bit and 64-bit plugins simultaneously, for those who still need the 32-bit one around. Until then, use the ~amd64 version for the 64-bit plugin and stable amd64 version for the 32-bit version.
Good news, everyone! As of net-www/netscape-flash-10.0.22.87 we have a true multilib ebuild. You get both 32-bit and 64-bit players on amd64, and if you set USE=-multilib, you just get the 64-bit player. Enjoy, and please test this ASAP, so we can stabilize it for security reasons :)
Looks good to me, I've set USE="-32bit -multilib" now, but -multilib seems to be ignored (masked). Whatever. Thanks a lot!
(In reply to comment #11) > Looks good to me, I've set USE="-32bit -multilib" now, but -multilib seems to > be ignored (masked). Whatever. Thanks a lot! Yes, this is due to my misunderstanding of the multilib flag: It is always forced on for anyone who has a multilib profile, and I originally thought it would do what the '32bit' flag does now - Which is to disable the 32-bit plugin for people with a multilib profile :)
