The new net-www/netscape-flash-10.0.22.87 ebuild tries to pull in and install x86_32 Flash on a desktop system with no 32bit browsers installed, *by default*. I appreciate the effort into introducing a multilib ebuild but this shouldn't be the default, there needs to be a way to disable installing the 32bit binary and avoid all the useless dependencies associated with it. Reproducible: Always
Could the ebuild just check to see if multilib USE variable is actually enabled? It seems to be ignoring it at the moment.
Yeah, I said the same in https://bugs.gentoo.org/260190#c6 The problem is, that at least on amd64-multilib profiles, the multilib USE flag cannot be unset without using /etc/portage/profile/package.use.mask And even when it is unset in that file, the ebuild still installs the 32bit version of libflashplayer. Reassigning to maintainer, CCing desktop-misc herd.
i'm in 64bit pure profile too so i'd like not to have 32 libs around
(In reply to comment #3) > i'm in 64bit pure profile too so i'd like not to have 32 libs around > That's what the 'no-multilib' profiles are for :) But all kidding aside, I'll look into this.
So, my misunderstanding was that you *could* actually turn off the multilib USE flag. However, it is forced on by all amd64 profiles except for 'no-multilib'. I suppose I'll have to come up with a different USE flag to mean what I *thought* 'multilib' meant. In the short term, I suppose as a workaround you could temporarily switch to a no-multilib profile, re-emerge this driver, then switch back to your original profile.
Okay, I've add a new USE flag called "32bit" so that: - If you are running a no-multilib profile, you get just the 64bit plugin. - If you are running a multilib profile, you by default get BOTH plugins. - You can now override this on multilib profiles with USE="-32bit": you will only the 64bit plugin. Wait a couple hours until the change hits the mirrors and resync your tree. You'll know you've got it when you see the new magic 32bit USE flag.
Jim, The Opera ebuild uses a "ia32" USE flag to install 32bit binaries *instead* of 64bit ones. Perhaps you should stick with that instead of "32bit"?
(In reply to comment #7) > The Opera ebuild uses a "ia32" USE flag to install 32bit binaries *instead* of > 64bit ones. Perhaps you should stick with that instead of "32bit"? Thanks for the suggestion. So, would "ia32" be a better fit? The description in use.local.desc says "Install 32-bit binaries instead of 64-bit binaries", which is opposite my intension for this flag: "Install the 32-bit plugin alongside the 64-bit plugin" A more general solution I am considering is working with the amd64 team to make 'multilib' more flexible, so I don't have to do this double-use-flag magic - This way 'multilib' could be overridden by users. So in conclusion, I think this will do as a local use-flag until such a time as this general solution is possible, and opera users won't be confused by its different meaning than "ia32". As Pontius Pilate said: "What I have written I have written"
