From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "Daniel Colascione" Newsgroups: gmane.emacs.devel Subject: Re: Finding the dump Date: Sun, 27 Jan 2019 22:28:06 -0800 Message-ID: References: <83munr8jb1.fsf@gnu.org> <838szb8ey9.fsf@gnu.org> <83d0oj62bc.fsf@gnu.org> <87ef8z4g1m.fsf@igel.home> <838sz75u7p.fsf@gnu.org> <877eer4e4x.fsf@igel.home> <835zub5p3i.fsf@gnu.org> <8736pf408v.fsf@igel.home> <83womq3z5c.fsf@gnu.org> <871s4yxfvb.fsf@igel.home> <83o9823xcq.fsf@gnu.org> <87womqvyy4.fsf@igel.home> <4f30b2b598e71d2c6ad766a3da8e4a33.squirrel@dancol.org> <87o982vszn.fsf@igel.home> <87k1ipx3jq.fsf@igel.home> <87bm41wzmv.fsf@igel.home> <837eep4fkj.fsf@gnu.org> <47a6df84-35b1-a85c-44be-5cec033e9255@cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="50753"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: SquirrelMail/1.4.23 [SVN] Cc: Eli Zaretskii , dancol@dancol.org, schwab@linux-m68k.org, rpluim@gmail.com, emacs-devel@gnu.org To: "Paul Eggert" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 28 07:28:34 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1go0PE-000CzK-VG for ged-emacs-devel@m.gmane.org; Mon, 28 Jan 2019 07:28:29 +0100 Original-Received: from localhost ([127.0.0.1]:54832 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1go0PD-0007mw-LN for ged-emacs-devel@m.gmane.org; Mon, 28 Jan 2019 01:28:27 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:53545) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1go0P7-0007mp-EZ for emacs-devel@gnu.org; Mon, 28 Jan 2019 01:28:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1go0P6-0004Vx-NL for emacs-devel@gnu.org; Mon, 28 Jan 2019 01:28:21 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:46708) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1go0P3-0004SE-PB; Mon, 28 Jan 2019 01:28:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=50A8ooHCRf0lf1F8+jey3fe6SMpfy9S/b0KSFG+cPKw=; b=iadpQVyJB7ItMz59/QLtYORnRXOZvPr1oKD44mSl7fO5RtC1gdE2JeP/DagDSOlGjh7Upl5U5GkB1MckjkY/0AVfA6+HkYqQ+Fvr8qGu3o4efYhsML38LyOyY7tEEaWdxE/DhZ4G/vddRAPDdR6l1PPcyX3ni0BOGsQB/NQI/8uWxWf79PzIFxDYVStPn6AGbdUFFj9YB/oTKlixyPKUfGSLyzGl2kiUFKo5fErrA/dsd0IgTtjtZ6FoV8QGtor8EA8a3iazqSqQ4tIu1hBijY2fqqQAfMcuTHeCAa0nPxqwtqfE4XJf1ITllSgvKVJUVb+sCObM+Qnj0uUHKh9tQw==; Original-Received: from localhost ([127.0.0.1] helo=dancol.org) by dancol.org with esmtp (Exim 4.84_2) (envelope-from ) id 1go0Os-00044c-0D; Sun, 27 Jan 2019 22:28:06 -0800 Original-Received: from 127.0.0.1 (SquirrelMail authenticated user dancol) by dancol.org with HTTP; Sun, 27 Jan 2019 22:28:06 -0800 In-Reply-To: <47a6df84-35b1-a85c-44be-5cec033e9255@cs.ucla.edu> X-Priority: 3 (Normal) Importance: Normal X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:232751 Archived-At: > Eli Zaretskii wrote: >>> I plan to look >>> into the possibility of putting the dump file inside the executable >>> (portably, >>> of course) so that Emacs startup needn't worry about finding the dump >>> file. This >>> would be significantly better for installers and users. >> I very much doubt that you could do that portably, let alone allow >> repeated dumping after the initial one. > > For repeated dumping without a C compiler present, we'd need to stick to > something like the current approach. But hardly anybody needs repeated > dumping, A lot more people will want repeated dumping once it's known to be viable. Baseline Emacs starts pretty fast, but starting Emacs for users with tons of packages and starter kits and things is still painful. With a custom dump file, all of that can go away. I've gotten a lot of interest in the approach already. > and those who do typically have a C compiler available, Requiring a C compiler at runtime is a non-starter. >> I really don't see why we should waste our energy on making the Emacs >> package one file less (out of 3000 it already has). > > This particular file is a bigger deal than the rest because Emacs cannot > run > without it. Emacs can run without all those other 3000 files. Not really it can't. There is no single-file distribution of Emacs. >> It certainly isn't a "hassle". > > It's already been a hassle for us, as seen in this thread. It will be a > hassle > for installers and maintainers too. The separate file also slows down > startup > compared to the approach I have in mind. I want to get out of the business of specially crafting executable files. Finding the dump file isn't any additional hassle for maintainers than finding any of the other numerous files we require today.