summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* app-admin/lastpass-binary-component: remove oldGöktürk Yüksek2020-02-121-114/+0
| | | | | Package-Manager: Portage-2.3.84, Repoman-2.3.20 Signed-off-by: Göktürk Yüksek <gokturk@gentoo.org>
* app-admin/lastpass-binary-component: Install to both firefox dirsLucian Poston2020-02-121-0/+116
| | | | | | | | | | | | | | | Firefox's directory for native messaging hosts is a compile-time variable. www-client/firefox-bin is set to a directory under /usr/lib/, while www-client/firefox varies. This -r1 bump will install to both locations so that both firefox and firefox-bin are able to locate the plugin. Closes: https://bugs.gentoo.org/688104 Closes: https://github.com/gentoo/gentoo/pull/14636 Bug: https://bugs.gentoo.org/687746 Package-Manager: Portage-2.3.84, Repoman-2.3.20 Signed-off-by: Lucian Poston <lucianposton@pm.me> Signed-off-by: Göktürk Yüksek <gokturk@gentoo.org>
* app-admin/lastpass-binary-component: Add RESTRICT=bindistMichał Górny2019-09-231-2/+2
| | | | Signed-off-by: Michał Górny <mgorny@gentoo.org>
* app-admin/lastpass-binary-component: Bump to version 4.19.0Stefan Kuhn2018-11-082-9/+5
| | | | | | | | | | Update SRC_URI, version bump to 4.19.0 according to https://lastpass.com/misc_download2.php Closes: https://bugs.gentoo.org/670116 Package-Manager: Portage-2.3.51, Repoman 2.3.11 Signed-off-by: Stefan Kuhn <stefan.kuhn.zurich@gmail.com> Signed-off-by: Göktürk Yüksek <gokturk@gentoo.org>
* app-admin/lastpass-binary-component: bump (!) and fix the fetch failure #640506Göktürk Yüksek2017-12-112-8/+53
| | | | | | | | | | | | | | | | | | | "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: fix the versioningGöktürk Yüksek2017-08-162-1/+1
| | | | | | | | | | | | The commit c11fc76d645ed4cebe6334273e4536f9f80ea1ca incorrectly bumps to the version 4.1.4 as opposed to 4.1.44. Because the upstream does not version their tarballs, it did not show up during testing. Moreover, the tarballs for the versions 4.1.2 and 4.1.44 are identical, so this mistake did not actually introduce any breakage. Because 4.1.44 > 4.1.4, there will be no downgrades or any unintended side effects either. Package-Manager: Portage-2.3.6, Repoman-2.3.1
* app-admin/lastpass-binary-component: bump to 4.1.44 #617536Göktürk Yüksek2017-05-222-2/+2
| | | | Package-Manager: Portage-2.3.3, Repoman-2.3.1
* Drop $Id$ per council decision in bug #611234.Robin H. Johnson2017-02-281-1/+0
| | | | Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
* app-admin/lastpass-binary-component: update maintainer email addressGöktürk Yüksek2016-05-181-1/+1
| | | | Package-Manager: portage-2.2.28
* app-admin/lastpass-binary-component: new package #571280Göktürk Yüksek2016-04-223-0/+95
This is a split off from app-admin/lastpass and only installs the binary component required by the browser extension, as opposed to installing the extension too. Beginning with lastpass-4, the upstream only installs the binary component. Also, add this package as a blocker for app-admin/lastpass. These two packages cannot be installed at the same time as that would introduce file collisions. Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=571280 Package-Manager: portage-2.2.26 (cherry picked from commit 6c8d1cd984fe45857ff9fac95ace41fddb1532b0) Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>