From: Muto <muto.lachen@tutanota.com>
To: Glenn Morris <rgm@gnu.org>, 26455@debbugs.gnu.org
Subject: bug#26455: Emacs Packaging
Date: Sun, 16 Apr 2017 06:25:59 +0200 (CEST) [thread overview]
Message-ID: <Khp-dwv--3-0@tutanota.com> (raw)
In-Reply-To: <bcziflif6j.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
Sorry for the late reply, been thinking it over.
I have to say I completely agree with you, to keep all the libraries up to date inside a .appimage package would be awkward to maintain.
Perhaps I'll write a tool to help simplify this method someday.
So about installing Emacs (the latest version), maybe have a list off packages the user needs for it, at least the packages that aren't usually installed by default, on the "Download" page?
e.g.:
To install Emacs from source, make sure you have the following packages installed:
build-essential texinfo libx11-dev libxpm-dev libjpeg-dev libpng-dev libgif-dev libtiff-dev libgtk2.0-dev libncurses-dev libxpm-dev automake autoconf
Then simply "./configure" "make" "make install"
Although, I'm not sure, many package names are different by other GNU/Linux distributions.
Sorry for the long letter, I'm sure you're really busy, but thank you for your time.
- -Stay paranoid. -Muto
https://mastodon.social/@MutoShack
12. Apr 2017 13:44 by rgm@gnu.org:
>
> PS If these technologies take off, this perhaps feels like something
> that should be addressed at the GNU level rather than the Emacs level.
> (Perhaps guix already provides some version of this?)
[-- Attachment #2: Type: text/html, Size: 1802 bytes --]
next prev parent reply other threads:[~2017-04-16 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 0:02 bug#26455: Emacs Packaging Muto
2017-04-12 19:39 ` Glenn Morris
2017-04-12 19:44 ` Glenn Morris
2017-04-16 4:25 ` Muto [this message]
2019-11-08 1:58 ` Stefan Kangas
2019-12-15 20:17 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Khp-dwv--3-0@tutanota.com \
--to=muto.lachen@tutanota.com \
--cc=26455@debbugs.gnu.org \
--cc=rgm@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).