From: UsernameRandomlyGenerated <UsernameRandomlyGenerated@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Git without perl
Date: Sat, 05 Feb 2022 18:33:33 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35419@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
New issue by UsernameRandomlyGenerated on void-packages repository
https://github.com/void-linux/void-packages/issues/35419
Description:
I saw the similar thread on reddit about having git without perl in repos and the explanation from Duncaen, but what if we turn it around and just add git-core subpackage that will not have all the perl dependencies? The main git package will still pull perl and work fine but we'll also have "core" one for people who want to save a little bit of space and/or network usage after fresh install.
next reply other threads:[~2022-02-05 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 17:33 UsernameRandomlyGenerated [this message]
2022-02-09 2:20 ` sgn
2022-02-09 2:22 ` sgn
2022-02-09 2:22 ` sgn
2022-03-07 14:47 ` sgn
2022-06-23 2:15 ` github-actions
2022-07-08 2:14 ` [ISSUE] [CLOSED] " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35419@inbox.vuxu.org \
--to=usernamerandomlygenerated@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).