From: Stefan Kangas <stefan@marxist.se>
To: Raffael Stocker <r.stocker@mnet-mail.de>
Cc: 38140@debbugs.gnu.org
Subject: bug#38140: ELPA needs a standard mechanism for single-package compilation
Date: Sat, 18 Jan 2020 11:45:18 +0100 [thread overview]
Message-ID: <87sgkdvy9t.fsf@marxist.se> (raw)
In-Reply-To: <874kzexazz.fsf@mnet-mail.de> (Raffael Stocker's message of "Fri, 08 Nov 2019 23:24:16 +0100")
Raffael Stocker <r.stocker@mnet-mail.de> writes:
> To compile a single ELPA package for tests or during development, it is
> currently necessary to clone/pull the whole elpa.git. This is wasteful
> if only a single package is of interest. ELPA should have a standard
> mechanism that allows (pulling/)compiling/testing etc. of single
> packages. I request that such a mechanism be implemented.
I don't think we want to split up elpa.git into many small ones to
support this use case, since the other side of the coin is that it
would make the job harder for the ELPA maintainers.
If you really want this, you could try "git clone --filter", but I'm
not sure if the GNU repositories are configured to allow for that.
Note also that there is already the possibility in ELPA to use an
external repository. This is optional and only used when there is a
specific need though, IIUC.
Best regards,
Stefan Kangas
PS. The repository is only 174 MB on my disk, which IMO is not that
much in this day and age.
next prev parent reply other threads:[~2020-01-18 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 22:24 bug#38140: ELPA needs a standard mechanism for single-package compilation Raffael Stocker
2020-01-18 10:45 ` Stefan Kangas [this message]
2020-01-18 15:30 ` Raffael Stocker
2020-01-18 16:55 ` Stefan Kangas
2020-11-28 18:50 ` Stefan Monnier
2021-04-21 22:28 ` 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=87sgkdvy9t.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=38140@debbugs.gnu.org \
--cc=r.stocker@mnet-mail.de \
/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).