From: WilliamBehrens <WilliamBehrens@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [Question] Hosting my own private mirror with only the packages I need
Date: Mon, 22 Nov 2021 20:02:20 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34205@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
New issue by WilliamBehrens on void-packages repository
https://github.com/void-linux/void-packages/issues/34205
Description:
I'm wanting to create my own custom mirror for void packages as I want to add a custom base-system and kernel but I don't think it would really be something to commit into the main void-packages repo. Something that I can't seem to find a direct answer too strangely is if it's possible to have multiple packages mirrors at once. So if I have my own custom repo hosted on my network and still be able to install packages from the main void repo. Another thing that isn't really documented if multiple repos is a thing is if each mirror has to host ALL of the packages in the main void repo or even if they just require the dependancies of the custom packages(like if I have a custom version of glew do I need to host my own version of glu or can glu be pulled from the main mirror to compile glew). I was hoping to be able to remove all the packages I'm not using to reduce the storage requirement of the mirror basically.
next reply other threads:[~2021-11-22 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 19:02 WilliamBehrens [this message]
2021-11-22 20:53 ` HadetTheUndying
2021-11-22 21:19 ` WilliamBehrens
2021-11-22 21:23 ` HadetTheUndying
2021-11-22 21:29 ` WilliamBehrens
2021-11-22 23:01 ` Duncaen
2021-11-22 23:09 ` Duncaen
2021-11-22 23:11 ` Duncaen
2021-11-23 11:17 ` Duncaen
2021-11-26 15:40 ` [ISSUE] [CLOSED] " WilliamBehrens
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-34205@inbox.vuxu.org \
--to=williambehrens@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).