Search Criteria
Package Details: vte4-notification 0.76.4-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/vte3-notification.git (read-only, click to copy) |
---|---|
Package Base: | vte3-notification |
Description: | Virtual Terminal Emulator widget for use with GTK4 with Fedora patches |
Upstream URL: | https://wiki.gnome.org/Apps/Terminal/VTE |
Keywords: | gnome |
Licenses: | LGPL |
Conflicts: | vte4 |
Provides: | libvte-2.91-gtk4.so, vte4 |
Submitter: | BerelTarMaciltur |
Maintainer: | mydongistiny |
Last Packager: | mydongistiny |
Votes: | 35 |
Popularity: | 0.000000 |
First Submitted: | 2015-03-29 22:27 (UTC) |
Last Updated: | 2024-08-26 15:39 (UTC) |
Dependencies (24)
- cairo (cairo-gitAUR)
- fribidi (fribidi-gitAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- gdk-pixbuf2 (gdk-pixbuf2-gitAUR)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- gnutls (gnutls-gitAUR)
- gtk4 (gtk4-customizableAUR, gtk4-paper-planeAUR, gtk4-gitAUR)
- icu (icu-gitAUR)
- lz4 (lz4-gitAUR)
- pango (pango-gitAUR)
- pcre2 (pcre2-gitAUR)
- systemd (systemd-chromiumosAUR, systemd-selinuxAUR, systemd-gitAUR, systemd-fmlAUR)
- systemd-libs (systemd-chromiumos-libsAUR, systemd-libs-selinuxAUR, systemd-libs-gitAUR, systemd-libs-fmlAUR)
- vte-notification-commonAUR
- at-spi2-core (at-spi2-core-gitAUR) (make)
- gi-docgen (make)
- git (git-gitAUR, git-glAUR) (make)
- gobject-introspection (make)
- gperf (gperf-gitAUR) (make)
- Show 4 more dependencies...
Required by (22)
- alpaca-ai (requires vte4)
- alpaca-git (requires vte4)
- apx-gui (requires vte4)
- atoms (requires vte4)
- batata (requires vte4)
- bigclick (requires vte4)
- blackbox-terminal (requires vte4)
- blackbox-terminal-git (requires vte4)
- envision-xr-git (requires vte4)
- gnome-builder-git (requires vte4)
- gnome-console-git (requires vte4)
- gnome-terminal-git (requires vte4)
- mwptools-git (requires vte4)
- neovim-gtk-git (requires vte4)
- pods (requires vte4)
- pods-git (requires vte4)
- ptyxis (requires vte4)
- seabird (requires vte4)
- tijolo (requires vte4)
- tijolo-git (requires vte4)
- Show 2 more...
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »
remspoor commented on 2020-06-14 14:30 (UTC)
@mydongistiny, Thanks!
I made a request to change
aur/libquotient
mydongistiny commented on 2020-06-12 16:03 (UTC)
@remspoor sounds like maybe the person who packaged libquotient did it incorrectly. Those headers should be going in with the rest of the qt files and not just in /usr/include. I also see they are using cmake with defines instead of using qmake like the rest of the qt packages in Arch use.
Try this PKGBUILD I edited for libquotient until the other one is fixed: https://pastebin.com/dZ0mP8Zm It moves the includes so QtCore/QLatin1String will be properly picked up.
remspoor commented on 2020-06-12 12:54 (UTC) (edited on 2020-06-12 12:57 (UTC) by remspoor)
Just to note: When
aur/libquotient
is installed the build fails with:It looks like it detects
/usr/include/util.h
I'm not sure if that
util.h
was meant to be the right one though.aaronrancsik commented on 2020-05-08 17:47 (UTC)
@mydongistiny Oh, nice! OK, thanks!
mydongistiny commented on 2020-05-06 19:05 (UTC) (edited on 2020-05-06 19:32 (UTC) by mydongistiny)
@aaronrancsik It's already been changed to that in the package.
Edit: Also, if you're using yay or another aur helper to build, make sure you are doing clean builds as the packages have changed.
aaronrancsik commented on 2020-05-06 14:53 (UTC) (edited on 2020-05-06 14:54 (UTC) by aaronrancsik)
My ugly workaround for:
bash: __vte_urlencode: command not found
edit: /etc/profile.d/vte.sh
replate
__vte_urlencode
with/usr/lib/vte-urlencode-cwd
and wait until it fixed...
amathadius commented on 2020-05-02 20:27 (UTC)
@Terence Notifications with zsh are actually broken for a while, yes.
Terence commented on 2020-03-30 00:23 (UTC)
Notifications are still broken for me with ZSH. Anyone else? and where should the issue be reported?
« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »