app-admin/lastpass-binary-component: bump (!) and fix the fetch failure #640506
authorGöktürk Yüksek <gokturk@gentoo.org>
Mon, 11 Dec 2017 00:52:35 +0000 (19:52 -0500)
committerGöktürk Yüksek <gokturk@gentoo.org>
Tue, 12 Dec 2017 02:55:43 +0000 (21:55 -0500)
commitb0fdfbee88ccedbcbd60305419104edc6183c65b
tree0f5ace5ee87538a4110adefbd6566bc6f4dc4427
parentbe3d7f08f2496cd21802420d5d5d16fb78f38c72
app-admin/lastpass-binary-component: bump (!) and fix the fetch failure #640506

"Let's extend LastPass support to Firefox using Native
Messaging. While doing so, let's modify our closed binary and change
who-knows-what too. And yeah, let's release it under the same version
4.1.44 because version bumps are sissies and only losers release
versioned tarballs."

Also separate the app manifest files for Chrome and Chromium because
allowed-origins are not the same. Add more comments to clarify the
file system locations for various installed files.

Update the postinst message to reflect that for some browsers users
have to enable the binary component manually after installing the
extension.

Closes: https://bugs.gentoo.org/640506
Package-Manager: Portage-2.3.8, Repoman-2.3.2
app-admin/lastpass-binary-component/Manifest
app-admin/lastpass-binary-component/lastpass-binary-component-4.1.44_p20171210.ebuild [moved from app-admin/lastpass-binary-component/lastpass-binary-component-4.1.44.ebuild with 51% similarity]