* bug#26455: Emacs Packaging
@ 2017-04-12 0:02 Muto
2017-04-12 19:39 ` Glenn Morris
0 siblings, 1 reply; 6+ messages in thread
From: Muto @ 2017-04-12 0:02 UTC (permalink / raw)
To: 26455
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
Request to alter the "recommended" way of installing Emacs in GNU/Linux:
Although technically not a bug, the "Download" section in the Emacs website is somewhat vague in describing how to install Emacs in GNU/Linux. Rather than the options "build from source" or "use an older version", I believe Emacs should ship packaged with a tool such as
AppImage (http://appimage.org)
Or FlatPak (http://flatpak.org).
This way installation on GNU/Linux systems would be simplified significantly and on top of that users would have easy access to the latest version rather than installing from a repository.
--Stay paranoid, and happy hacking! -Muto
https://mastodon.social/@MutoShack
[-- Attachment #2: Type: text/html, Size: 1160 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#26455: Emacs Packaging
2017-04-12 0:02 bug#26455: Emacs Packaging Muto
@ 2017-04-12 19:39 ` Glenn Morris
2017-04-12 19:44 ` Glenn Morris
2019-11-08 1:58 ` Stefan Kangas
0 siblings, 2 replies; 6+ messages in thread
From: Glenn Morris @ 2017-04-12 19:39 UTC (permalink / raw)
To: Muto; +Cc: 26455
Muto wrote:
> Although technically not a bug, the "Download" section in the Emacs
> website is somewhat vague in describing how to install Emacs in
> GNU/Linux. Rather than the options "build from source" or "use an
> older version", I believe Emacs should ship packaged with a tool such
> as
> AppImage (http://appimage.org)
> Or FlatPak (http://flatpak.org).
> This way installation on GNU/Linux systems would be simplified
> significantly and on top of that users would have easy access to the
> latest version rather than installing from a repository.
Staying paranoid as requested:
Do these approaches mean that the Emacs developers then become
responsible for shipping all the required dependent libraries,
monitoring them for security issues, and updating them when needed,
rather than relying on the distribution to do that?
> --Stay paranoid, and happy hacking! -Muto
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#26455: Emacs Packaging
2017-04-12 19:39 ` Glenn Morris
@ 2017-04-12 19:44 ` Glenn Morris
2017-04-16 4:25 ` Muto
2019-11-08 1:58 ` Stefan Kangas
1 sibling, 1 reply; 6+ messages in thread
From: Glenn Morris @ 2017-04-12 19:44 UTC (permalink / raw)
To: Muto; +Cc: 26455
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?)
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#26455: Emacs Packaging
2017-04-12 19:44 ` Glenn Morris
@ 2017-04-16 4:25 ` Muto
0 siblings, 0 replies; 6+ messages in thread
From: Muto @ 2017-04-16 4:25 UTC (permalink / raw)
To: Glenn Morris, 26455
[-- 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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#26455: Emacs Packaging
2017-04-12 19:39 ` Glenn Morris
2017-04-12 19:44 ` Glenn Morris
@ 2019-11-08 1:58 ` Stefan Kangas
2019-12-15 20:17 ` Stefan Kangas
1 sibling, 1 reply; 6+ messages in thread
From: Stefan Kangas @ 2019-11-08 1:58 UTC (permalink / raw)
To: Glenn Morris; +Cc: Muto, 26455
Glenn Morris <rgm@gnu.org> writes:
> Muto wrote:
>
>> Although technically not a bug, the "Download" section in the Emacs
>> website is somewhat vague in describing how to install Emacs in
>> GNU/Linux. Rather than the options "build from source" or "use an
>> older version", I believe Emacs should ship packaged with a tool such
>> as
>> AppImage (http://appimage.org)
>> Or FlatPak (http://flatpak.org).
>> This way installation on GNU/Linux systems would be simplified
>> significantly and on top of that users would have easy access to the
>> latest version rather than installing from a repository.
>
> Staying paranoid as requested:
>
> Do these approaches mean that the Emacs developers then become
> responsible for shipping all the required dependent libraries,
> monitoring them for security issues, and updating them when needed,
> rather than relying on the distribution to do that?
>
>> --Stay paranoid, and happy hacking! -Muto
Glenn Morris <rgm@gnu.org> writes:
> 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?)
While I think this is not a bad idea in and of itself, I think this is
beyond the scope of the Emacs project at the moment given our scarce
resources. Or perhaps it's better addressed at the GNU level as Glenn
suggests.
I'd therefore suggest to close this as wontfix. Any other opinions?
Best regards,
Stefan Kangas
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#26455: Emacs Packaging
2019-11-08 1:58 ` Stefan Kangas
@ 2019-12-15 20:17 ` Stefan Kangas
0 siblings, 0 replies; 6+ messages in thread
From: Stefan Kangas @ 2019-12-15 20:17 UTC (permalink / raw)
To: Glenn Morris; +Cc: Muto, 26455
tags 26455 + wontfix
close 26455
thanks
Stefan Kangas <stefan@marxist.se> writes:
> Glenn Morris <rgm@gnu.org> writes:
>
>> 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?)
>
> While I think this is not a bad idea in and of itself, I think this is
> beyond the scope of the Emacs project at the moment given our scarce
> resources. Or perhaps it's better addressed at the GNU level as Glenn
> suggests.
>
> I'd therefore suggest to close this as wontfix. Any other opinions?
No further comments within 5 weeks, so I'm closing this as wontfix.
Best regards,
Stefan Kangas
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-12-15 20:17 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2019-11-08 1:58 ` Stefan Kangas
2019-12-15 20:17 ` Stefan Kangas
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).