From: "Andrew Ammerlaan" <andrewammerlaan@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: app-editors/visual-studio-code-bin/
Date: Tue, 9 Feb 2021 14:46:13 +0000 (UTC) [thread overview]
Message-ID: <1612739596.973ad60d28d19f15a983708e476b1a744fab89d1.andrewammerlaan@gentoo> (raw)
commit: 973ad60d28d19f15a983708e476b1a744fab89d1
Author: Ross Charles Campbell <rossbridger.cc <AT> gmail <DOT> com>
AuthorDate: Sun Feb 7 23:12:50 2021 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
CommitDate: Sun Feb 7 23:13:16 2021 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=973ad60d
app-editors/visual-studio-code-bin: fix issues on desktop files
Closes: https://bugs.gentoo.org/769344
Package-Manager: Portage-3.0.14, Repoman-3.0.2
Signed-off-by: Ross Charles Campbell <rossbridger.cc <AT> gmail.com>
.../visual-studio-code-bin-1.53.0.ebuild | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/app-editors/visual-studio-code-bin/visual-studio-code-bin-1.53.0.ebuild b/app-editors/visual-studio-code-bin/visual-studio-code-bin-1.53.0.ebuild
index 4d781191..e36c20b3 100644
--- a/app-editors/visual-studio-code-bin/visual-studio-code-bin-1.53.0.ebuild
+++ b/app-editors/visual-studio-code-bin/visual-studio-code-bin-1.53.0.ebuild
@@ -3,7 +3,7 @@
EAPI=7
-inherit desktop eutils pax-utils
+inherit desktop eutils pax-utils xdg
DESCRIPTION="Multiplatform Visual Studio Code from Microsoft"
HOMEPAGE="https://code.visualstudio.com"
@@ -60,7 +60,7 @@ src_install() {
insinto "/opt/${PN}"
doins -r *
fperms +x /opt/${PN}/{,bin/}code
- dosym "../../opt/${PN}/bin/code" "usr/bin/${PN}"
+ dosym "../../opt/${PN}/bin/code" "usr/bin/code"
domenu "${FILESDIR}/code.desktop"
domenu "${FILESDIR}/code-url-handler.desktop"
dodoc "resources/app/LICENSE.rtf"
@@ -68,6 +68,13 @@ src_install() {
}
pkg_postinst() {
+ xdg_desktop_database_update
+ xdg_mimeinfo_database_update
elog "You may want to install some additional utils, check in:"
elog "https://code.visualstudio.com/Docs/setup#_additional-tools"
}
+
+pkg_postrm() {
+ xdg_desktop_database_update
+ xdg_mimeinfo_database_update
+}
next reply other threads:[~2021-02-09 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 14:46 Andrew Ammerlaan [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-15 17:42 [gentoo-commits] repo/proj/guru:master commit in: app-editors/visual-studio-code-bin/ Andrew Ammerlaan
2021-05-09 18:13 Andrew Ammerlaan
2021-04-23 8:47 Haelwenn Monnier
2021-04-23 8:47 Haelwenn Monnier
2021-04-19 7:40 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2021-04-19 8:04 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-04-18 15:47 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2021-04-18 16:01 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-04-18 9:10 Andrew Ammerlaan
2021-04-17 20:00 Andrew Ammerlaan
2021-04-06 9:03 Andrew Ammerlaan
2021-03-13 12:26 Andrew Ammerlaan
2021-03-05 12:10 Andrew Ammerlaan
2021-02-13 11:42 Andrew Ammerlaan
2021-02-11 19:27 Andrew Ammerlaan
2021-02-09 14:46 Andrew Ammerlaan
2021-02-05 12:19 Andrew Ammerlaan
2021-01-04 9:34 Andrew Ammerlaan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1612739596.973ad60d28d19f15a983708e476b1a744fab89d1.andrewammerlaan@gentoo \
--to=andrewammerlaan@riseup.net \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox