[arch-multilib] Renaming flashplugin

Heiko Baums lists at baums-on-web.de
Sun Oct 24 10:06:36 EDT 2010

Am Sun, 24 Oct 2010 11:58:46 +0200
schrieb Thomas Bächler <thomas at archlinux.org>:

> For a smooth support, install and upgrade procedure, I would do the
> renaming at the same time as moving in the native plugin. And I won't
> believe continued 64 bit support from Adobe until they start shipping
> it as a stable release.

Was the previous native 64 bit version every stable? As far as I know
it was not. Is Flash stable at all?

I second Pierre's suggestion. This way everyone who wants the "stable"
32 bit Flash can install lib32-flashplugin or bin32-flashplugin and
everyone who wants the native 64 bit pre version can install
flashplugin. Except there are serious instabilities, bugs or
vulnerabilities. In this case the pre version should of course not be

But I'd choose one of the names lib32-flashplugin or bin32-flashplugin
over flashplugin-nspluginwrapper because it's clearer and says what
it's for.

Notwithstanding the above, I think the package in [multilib] should be
renamed. A package name without an appendix like lib32- is usually meant
to be a native package for the corresponding architecture.


More information about the arch-multilib mailing list