Search Criteria
Package Details: vte-common-git 0.79.0.r39.gd99a527c-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/vte-git.git (read-only, click to copy) |
---|---|
Package Base: | vte-git |
Description: | Virtual Terminal Emulator widget (common files) |
Upstream URL: | https://gitlab.gnome.org/GNOME/vte |
Licenses: | GPL-3.0-or-later, LGPL-3.0-or-later |
Conflicts: | vte-common |
Provides: | vte-common |
Submitter: | tallero |
Maintainer: | xiota |
Last Packager: | xiota |
Votes: | 1 |
Popularity: | 0.000024 |
First Submitted: | 2023-06-27 15:15 (UTC) |
Last Updated: | 2024-11-11 06:31 (UTC) |
Dependencies (12)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- cairo (cairo-gitAUR) (make)
- fast_float (fast_float-gitAUR) (make)
- gi-docgen (make)
- git (git-gitAUR, git-glAUR) (make)
- glib2-devel (make)
- gobject-introspection (make)
- gperf (gperf-gitAUR) (make)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR) (make)
- gtk4 (gtk4-customizableAUR, gtk4-paper-planeAUR, gtk4-gitAUR) (make)
- meson (meson-gitAUR) (make)
- vala (vala-gitAUR) (make)
Required by (6)
- termite (requires vte-common)
- termite-git (requires vte-common)
- vte-legacy (requires vte-common)
- vte290 (requires vte-common)
- vte3-git (requires vte-common)
- vte4-git (requires vte-common)
Latest Comments
xiota commented on 2023-11-15 00:22 (UTC)
Package has been synced with extra. Tested in clean chroot.
a821 commented on 2023-07-05 16:51 (UTC)
Fails to build with
extra-x64_64-build
:What is this line supposed to do?
tallero commented on 2023-07-05 10:27 (UTC) (edited on 2023-07-05 12:55 (UTC) by tallero)
The @smnpk user writes as reason for its (incorrect) deletion request:
This package correctly split git versions of
vte3
,vte4
andvte-common
under a singlepkgbase
(i.e. a single build); the packages he mentions has a different structure, indeed a questionable one (currently it still requires users to installgtk3
to obtain a workingvte4
and it also requires two separate builds).I maintain most of the
-git
GNOME stack, I am a GNOME app developer, I follow changes upstream closely.I have been writing all week the either inexpert or trolling
vte3-git
andvte4-git
"contributor" his packages have issues.I'd like to underline I normally never take such a stance as defining someone "inexpert" or "trolling", but really this person is trying to escalate this issue without any clear reason.
He denied proposed fixes' usefulness each and every time, still always applying them and then saying they were not needed. Probably tomorrow his package will be identical to this and he will open a duplicate request, say I even bothered him.
Up to now he has kept his very questionable technical decision to keep two
pkgbase
s.You should read all the comments, all the code and compare dates to find that this person is actively trying to make me look like the bad guy when instead he is the one who has been aggressive, non-cooperating and hostile the whole time.
What is happening is really shameful. I feel this person should be punished somehow; still he is free to probably use alternative accounts just to keep trolling here.
It's a week I am being attacked personally for having gently suggested someone how to fix a package up to the point of making for him an entirely new package so it would have been easier to apply the changes and merge the packages.
I literally showed this rude brute who went mad a month ago because he couldn't build a package in his local tree and so decided it was okay to defame me without even trying to reach me beyond the "flag out-of-date" button how to properly contribute and be polite when a maintainer is missing or is non-cooperating and this is the result, that I have to defend myself publicly on
aur-general
. What a clown world.I am sorry but I can only define as toxic someone you are trying to help and shorten his work and instead keeps "punching" you and defaming you.
Please everyone be aware of these dangerous toxic trolls.
tallero commented on 2023-07-04 20:05 (UTC) (edited on 2023-07-04 20:09 (UTC) by tallero)
Since @xiota still doesn't want to fix his packages, I made
vte-git
the git version of upstream (extra
repo)vte4
;vtethree-git
the git version of upstreamvte3
;vte-common-git
the git version of upstreamvte-common
.tallero commented on 2023-07-02 06:37 (UTC) (edited on 2023-07-02 06:53 (UTC) by tallero)
@xiota: you need to update your packages or merge with this one, it's known that it's not currently compatible with yours, which are outdated (unsplit).
About contacting maintainers privately in advance to update the package, while I can agree it's certainly more fun when it happens, it's totally absurd and insane to think to do so every single time.
In general, if doesn't take you 3 minutes to split or combine a package and you need emails to discuss something such as this, then maybe you should change approach.