-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Support]: Advice on dealing with mono-repos #318
Comments
What is the output of |
Hmm, maybe something like this is possible: https://github.blog/2020-01-17-bring-your-monorepo-down-to-size-with-sparse-checkout/#cloning-in-sparse-mode
|
I've considered using sparse checkouts. |
Confirmation
Elpaca Version
Elpaca bc685f5 HEAD -> master, origin/master, origin/HEAD
installer: 0.7
emacs-version: GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41, cairo version 1.18.0)
of 2024-04-23
git --version: git version 2.45.2
Operating System
Windows Subsystem for Linux - Arch Linux; Windows 11
Description
Hi. Currently I've a couple of packages that live in mono-repos:
flymake
(in the emacs repo) and the commercial-emacs variantgnus
.These clone the whole repository and subsequently clutter the fetch process with all changes to the repo. Do you have any tips on avoiding this? I see there's some internal mono-repo handling in
elpaca.el
but it's over my head, I don't understand what it does.This is the recipe I'm using for flymake (it's the one on the GNU-Devel menu):
The text was updated successfully, but these errors were encountered: