Package Details: emacs-git 30.0.50.169253-1

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)

Required by (313)

Sources (2)

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 the emacs-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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 39 Next › Last »

MormonJesus69420 commented on 2022-04-08 18:20 (UTC)

That's understandable, enjoy your holidays!

toropisco commented on 2022-04-08 18:04 (UTC)

Hmmm... MormonJesus69420 you are correct after all. I don't have much time this week and I'm not even reading non-work email with much attention. I was left with with your first message and jumbled memories. I'll fix it during Easter week.

MormonJesus69420 commented on 2022-04-08 17:05 (UTC)

Hi toropisco! I'm not sure I understand you correctly. Do you mean I read the PKGBUILD wrongly? As far as I can tell the line 232 doesn't need to be there. However I have very little experience with both writing and reading PKGBUILD files, so I would appreciate it if you could elaborate on your comment. Thank you for your time in replying to my comment.

toropisco commented on 2022-04-08 16:45 (UTC)

MormonJesus69420 I just stole some time to examine my project files. You need a new recipe for your reading glasses. :-)

toropisco commented on 2022-04-07 16:26 (UTC)

Hi MormonJesus69420, it is simply that the option did exist last time I did a full walkthrough on the script. This is the master development source code tip after all.

I'll remove it next time I do a new cleanup.

MormonJesus69420 commented on 2022-04-07 13:38 (UTC) (edited on 2022-04-07 13:38 (UTC) by MormonJesus69420)

Hey I was looking at the PKGBUILD for this package and noticed something that I think is off.

On line 232 we have following:

--with-sound=alsa

Which as far as I am aware enables sound by default, even though there's an option on line 64 to enable the alsa support. The script checks for that ALSA flag further down on lines 280-284, as follows:

if [[ $ALSA == "YES" ]]; then
    _conf+=( '--with-sound=alsa' );
else
    _conf+=( '--with-sound=no' );
fi

Shouldn't therefore the line 232 be removed?

clangdo commented on 2022-04-04 21:15 (UTC)

The https URL I can currently access is: https://git.savannah.gnu.org/git/emacs.git, notice the extra /git/ in the link. I would recommend using this if it works because at least you have some TLS on top of the connection. Otherwise you have NO verification that the code your running is from the GNU project. Another option would be to do GPG verification, but every commit on the master branch probably isn't signed?

See this gist for why you should prefer https https://gist.github.com/grawity/4392747.

xircon commented on 2022-03-22 19:32 (UTC)

Something is obviously wrong with my set-up, am investigating.

xircon commented on 2022-03-22 19:28 (UTC)

What? I just cloned the PKGBUILD!

toropisco commented on 2022-03-22 19:07 (UTC)

@xircon Why do you insist on using https for cloning? I updated the PKGBUILD to use the protocol at least six months ago.