Nealsid. Instead of polluting this package forum thread section with low quality comments, your fellow AUR users and myself, the maintainer who actually added support for pgtk three years ago, would appreciate if your read makepkg's man page and made yourself familiar with the -p flag.
Search Criteria
Package Details: emacs-git 30.0.50.169253-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/emacs-git.git (read-only, click to copy) |
---|---|
Package Base: | emacs-git |
Description: | GNU Emacs. Development master branch. |
Upstream URL: | http://www.gnu.org/software/emacs/ |
Keywords: | development editor IDE text |
Licenses: | GPL3 |
Conflicts: | emacs |
Provides: | emacs |
Submitter: | toropisco |
Maintainer: | toropisco |
Last Packager: | toropisco |
Votes: | 107 |
Popularity: | 1.93 |
First Submitted: | 2014-01-05 02:05 (UTC) |
Last Updated: | 2023-10-14 18:36 (UTC) |
Dependencies (23)
- cairo (cairo-gitAUR)
- giflib (giflib-gitAUR)
- gnutls (gnutls-gitAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- harfbuzz (harfbuzz-gitAUR)
- jansson (jansson-gitAUR)
- libgccjit (libgccjit-gitAUR, libgccjit-snapshotAUR)
- libjpeg-turbo (mozjpeg-gitAUR, libjpeg-turbo-gitAUR, mozjpegAUR)
- libotf
- libpng (libpng-gitAUR, libpng-apngAUR)
- libsm
- libtiff (libtiff-gitAUR, libtiff-lercAUR)
- libwebp (libwebp-gitAUR)
- libxcb (libxcb-gitAUR)
- libxi (libxi-gitAUR)
- libxml2 (libxml2-gitAUR, libxml2-2.9AUR)
- libxpm (libxpm-gitAUR)
- sqlite3 (sqlite)
- tree-sitter (tree-sitter-gitAUR)
- xcb-util
- git (git-gitAUR, git-glAUR) (make)
- libxi (libxi-gitAUR) (make)
- xorgproto (xorgproto-gitAUR) (make)
Required by (313)
- anthy-unicode (requires emacs) (make)
- anthy-unicode-git (requires emacs) (make)
- astroid-git (requires emacs) (optional)
- auctex (requires emacs)
- auctex-git (requires emacs)
- auto-complete-nxml-git (requires emacs)
- auto-complete-nxml-git (requires emacs) (make)
- bbdb (requires emacs)
- bigloo-devel (requires emacs) (make)
- bigloo-devel (requires emacs) (optional)
- carp (requires emacs) (make)
- cask (requires emacs)
- cask-git (requires emacs)
- cmake-git (requires emacs) (make)
- csvedepli (requires emacs) (make)
- dictionary (requires emacs)
- distel (requires emacs)
- dmscripts-git (requires emacs) (optional)
- eldev-git (requires emacs)
- eless (requires emacs)
- Show 293 more...
Sources (2)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 .. 39 Next › Last »
toropisco commented on 2023-05-13 20:11 (UTC)
toropisco commented on 2023-05-13 20:11 (UTC)
Nealsid. Instead of polluting this package forum thread section with low quality comments, your fellow AUR users and myself, the maintainer who actually added support for pgtk three years ago, would appreciate if your read makepkg's man page and made yourself familiar with the -p flag.
Nealsid commented on 2023-05-09 22:47 (UTC) (edited on 2023-05-09 22:47 (UTC) by Nealsid)
If anyone wants to build with Wayland support, I had to make the following patch (but I'm not sure how the package version difference snuck in there)
diff --git a/PKGBUILD b/PKGBUILD
index 0b35e4a..c4379f0 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -50,12 +50,12 @@ GPM= # Mouse support in Linux console using gpmd.
NOTKIT= # Use no toolkit widgets. Like B&W Twm (001d sk00l).
# Bitmap fonts only, 1337!
-
-PGTK= # Use native GTK3 build. Supports Wayland, yay! Still
+
+PGTK="YES" # Use native GTK3 build. Supports Wayland, yay! Still
# has some problems if running under Xorg. Remember,
# this is my personal build file!
-GTK3="YES" # GTK3 old windowing interface.
+GTK3= # GTK3 old windowing interface.
LUCID= # Use the lucid, a.k.a athena, toolkit. Like XEmacs, sorta.
#
@@ -93,7 +93,7 @@ if [[ $CLI == "YES" ]] ; then
else
pkgname="emacs-git"
fi
-pkgver=30.0.50.165856
+pkgver=30.0.50.166196
pkgrel=1
pkgdesc="GNU Emacs. Development master branch."
arch=('x86_64')
snackattack commented on 2023-02-16 23:22 (UTC) (edited on 2023-02-17 14:11 (UTC) by snackattack)
You are soooo GenZ that vou can see beyond your navel.
Second, yes it seems there's a bug that seems to be relatively recent. I've already fixed it in my repository, but... Should I give it to you today, you entitled brat?
This is really inappropriate, and violates Arch code of conduct, see the sections on respect, flaming, and ranting.
ykelvis commented on 2023-02-16 01:45 (UTC)
in the case of replace
, i think it is indeed misused. it is used to replace obsolete packages, emacs obviously is not.1 as said in wiki, alternative package in aur should use conflict
and provide
instead of replace
.
if a user has emacs
installed and is using a repo that has this package prebuilt, when doing a Syu
there would be prompt like "Replace emacs with emacs-git?[Y/n]", because replace
makes pacman think emacs
is obsolete. the more resonable behaviour should be prompting conflict issus when user explicitly wants to install emacs-git
.
this happened in our repo, but if the user only use aur and official repos, that would be fine. 2
Hi-Angel commented on 2023-02-15 17:01 (UTC)
@toropisco I am sorry I didn't give enough details, you are right.
Regarding my reply: I just followed your tone, so your advises about emotional intelligence, etc, ain't really on-topic. Your reply about "replaces/conflicts" was something along the lines "RTFM". You could've said "you are wrong because X says this, and Y mentions that, read manual for details". Instead you basically said "go read the docs", which feels like arrogance, so of course I got annoyed and replied sarcastically.
I'm sorry, either way, I am thankful you are maintaining this package.
toropisco commented on 2023-02-15 16:49 (UTC) (edited on 2023-02-15 16:50 (UTC) by toropisco)
Sigh. Child, when you want to report a bug, you report a bug with details. Don't start going tangentially and finish with a tantrum full of insults. You are soooo GenZ that vou can see beyond your navel.
First, learn how to report bugs properly. Something along the line: "I have this problem. The details are so and so. I've looked into this and this seems to be the fix". The maintainer may or may not use your fix, but will be thankful that you reported something that needs to be corrected.
Second, yes it seems there's a bug that seems to be relatively recent. I've already fixed it in my repository, but... Should I give it to you today, you entitled brat?
Third, learn to behave socially. I strongly recomment you read these two books:
Hi-Angel commented on 2023-02-15 16:09 (UTC)
@Hi-Angel, your request is unreasonable.
So, you claim that it is reasonable that when I tried installing emacs-git I didn't get a query "do you want to remove emacs", and when I out of curiosity pressed "yes, I want to continue", pacman failed with a wall of text about conflicting files?
Ha, alright. Folks, anybody else considers that reasonable as well? Might be the new trend in package management that I missed, sorry 🤷♂️
toropisco commented on 2023-02-15 15:19 (UTC)
@Hi-Angel, your request is unreasonable.
Three learning hints:
-
Install emacs-git; run pacman -Ql on it.
-
Run pacman -Fy, then run pacman -Fl on emacs.
-
Compare outputs, giving careful attention to the contents of /usr/bin
Question: Do you see why you are wrong in your assertions and request?
Finally, read PKGBUILD(5) and pacman(8) for further enlightenment.
Cheers.
Hi-Angel commented on 2023-02-15 09:31 (UTC) (edited on 2023-02-15 17:23 (UTC) by Hi-Angel)
For some reason while installing this package and having the usual emacs
package installed, pacman doesn't see it as a conflict.
I think the replaces=('emacs')
needs to be changed to conflicts=('emacs')
. It's done this way in i3-git and I confirm that works.
Pinned Comments
toropisco commented on 2017-06-30 19:14 (UTC) (edited on 2022-05-15 13:26 (UTC) by toropisco)
This PKGBUILD is a work in progress. If you find PACKAGING bugs, please let me know ASAP.
Upstream bugs are to be reported upstream. Check out the emacs-devel archives to confirm if this is an already known bug. In fact... Why are you not subscribed to
emacs-devel
?. Also check theemacs-bug-tracker
archives.Reporting bugs: Write to the Emacs Bug Tracker and report it there. Or, better yet, use the
debbugs
client included with the text editor. You will find instructions at https://debbugs.gnu.org/. Good luck!If you confirm it is a packaging bug, you are welcome to report it here.
Yaourt and other automated tools users BEWARE! This PKGBUILD is written with hand updating in mind and I won't fix bugs arising from such use. Besides, cloning the same repository time and time again from a non-profit such as the GNU Project/FSF gives out a very low image of you.