From: Hugo Thunnissen <devel@hugot.nl>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Preferred approach to inclusion of data in ELPA package
Date: Sat, 19 Aug 2023 13:26:30 +0200 [thread overview]
Message-ID: <da49f9a2-a211-fe90-f5cf-7ee404066680@hugot.nl> (raw)
In-Reply-To: <878ra91ie7.fsf@posteo.net>
On 8/17/23 23:14, Philip Kaludercic wrote:
>
> Another idea is to have a Makefile generate the file, like the one you
> describe in option 2., that is generate whenever the package is built
> and bundled into a tarball for distribution. That way you don't have to
> store a binary blob in your repository, and you can avoid burdening the
> user with additional computations at either compile or runtime.
>
> Does the generation require any special functionality/tools/code to be
> provided on the device the index is generated on?
The php function/class stubs are generated with a php script, but I'm
checking the resulting stubs file into git. The index itself can be
built with just my package based on the stubs file.
Some more context, as I built and bench-marked a prototype: The
resulting index file is 3.1MB of s-expressions which when compressed
with gzip becomes a file of 172K (there's a lot of duplicate
symbols/strings in there). Loading this file takes about 30% less time
than building the index from scratch (300ms vs 430-450ms on my laptop
with Core i5-8250U, byte compiled). I suppose this could be further
optimized with a more efficient serialization format, but I don't want
to spend much time on implementing that as I'm working towards an
initial package release.
How would having a Makefile like you suggest work in practice? Would I
need to request that the ELPA maintainers add my Makefile to the build
process of my package somehow? Or is there a standard automated way to
have Makefiles be executed during an ELPA build?
Also: If the former is the case, is the reduction in load time that this
brings even significant enough to be worth the bother or should I just
hold off on this while I look for a more efficient solution?
next prev parent reply other threads:[~2023-08-19 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 13:58 Preferred approach to inclusion of data in ELPA package Hugo Thunnissen
2023-08-17 21:14 ` Philip Kaludercic
2023-08-19 11:26 ` Hugo Thunnissen [this message]
2023-08-19 15:51 ` Philip Kaludercic
2023-08-20 19:24 ` Hugo Thunnissen
2023-08-20 20:42 ` Philip Kaludercic
2023-08-29 8:41 ` Hugo Thunnissen
2023-08-30 19:27 ` Philip Kaludercic
2023-08-20 13:30 ` sbaugh
2023-08-20 17:47 ` Hugo Thunnissen
2023-08-20 19:43 ` Hugo Thunnissen
2023-08-20 22:59 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=da49f9a2-a211-fe90-f5cf-7ee404066680@hugot.nl \
--to=devel@hugot.nl \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.