Soylens, you have no packages at your name. Or of you do you are using an account exclusively to harass other AUR contributors?
Be aware that AUR contains user contributions and the emacs-git package reflects my usage, being the author. Not yours.
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) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 39 Next › Last »
Soylens, you have no packages at your name. Or of you do you are using an account exclusively to harass other AUR contributors?
Be aware that AUR contains user contributions and the emacs-git package reflects my usage, being the author. Not yours.
Why is nemacs
even a thing?
I can understand that it might be occasionally useful. I just don't find it a reasonable thing to include into any package. It is not part of the standard emacs one would expect, and it is just an ugly solution to whatever problem that's meant to be solved.
I'd suggest leaving it to the user to set up a shell alias instead, since it doesn't serve any purpose elsewhere. You don't use such shorthands in scripts anyway.
It basically saves three characters in total. Just imagine having a /usr/bin/ll
.
If many people have puresize limit errors, it is an upstream bug.
After a recompilation I got a warning about puresize to be too small today. The elisp manual recommends increasing SYSTEM_PURESIZE_EXTRA in puresize.h in such cases.
diff --git a/src/puresize.h b/src/puresize.h
index 5516747ac2b..2f59ebc4ebe 100644
--- a/src/puresize.h
+++ b/src/puresize.h
@@ -39,7 +39,7 @@ #define EMACS_PURESIZE_H
amount of storage. This is a lot more update-robust that defining
BASE_PURESIZE or even PURESIZE directly. */
#ifndef SYSTEM_PURESIZE_EXTRA
-#define SYSTEM_PURESIZE_EXTRA 0
+#define SYSTEM_PURESIZE_EXTRA 140000
#endif
#ifndef SITELOAD_PURESIZE_EXTRA
100000 was not enough for me, but it may vary.
Attempting to build emacs-git
this morning results in the following error message:
$ makepkg -C -i
==> Making package: emacs-git 29.0.50.157115-1 (Tue 05 Jul 2022 10:22:41 AM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating emacs-git git repo...
-> Found nemacs
==> Validating source files with b2sums...
emacs-git ... Skipped
nemacs ... Passed
==> Extracting sources...
-> Creating working copy of emacs-git git repo...
Switched to a new branch 'makepkg'
==> Starting prepare()...
==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: AC_INIT([GNU Emacs], [29.0.50], [bug-gnu-emacs@gnu.org], [],.157927
Maybe due to commit 59206529a17a8ae976072d8306882c4ff37a2fbd?
You can fix this by applying the following patch to PKGBUILD
diff --git a/PKGBUILD b/PKGBUILD
index db061ba..df24151 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -201,7 +201,7 @@ pkgver() {
printf "%s.%s" \
"$(grep AC_INIT configure.ac | \
- sed -e 's/^.\+\ \([0-9]\+\.[0-9]\+\.[0-9]\+\?\).\+$/\1/')" \
+ sed -e 's/^.\+\ \[\([0-9]\+\.[0-9]\+\.[0-9]\+\?\)\].\+$/\1/')" \
"$(git rev-list --count HEAD)"
}
It seems a new makedep is missing: configure: error: The following required libraries were not found:
libXpm
Maybe some development libraries/packages are missing?
To build anyway, give:
--with-xpm=ifavailable
Why remove the AOT
configuration in the recent commits? It seems that we still need this option (NATIVE_FULL_AOT
) to compile the lisp code to native code.
Reference: https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/Makefile.in?h=master#n35
All pkgbuild can be corrected, ffmpeg variants are usually correct and there are many, can't see why can't do the same
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.