Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Restructuring/Organizing general Packages etc.
Date: Mon, 01 Jan 2024 14:32:27 +0100	[thread overview]
Message-ID: <20240101133227.aT2lZOs3HB0SRE674IG3afQ02ZCLU1JX7dQTj_et2dk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48014@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/48014#issuecomment-1873330045

Comment:
There is absolutely no way it would make anything easier to run in the long run, @classabbyamp has a more in-depth understanding of how this repository works.

Even simple packages have chains of dependencies that go into hundreds of packages, orchestrating changes through multiple git repositories is simply not feasible. Large organization use mono-repos for similar reasons, it just makes everything easier to manage and orchestrate and its not like our repository is that big either, the only big problem is the single large `srcpkgs` directory.


  parent reply	other threads:[~2024-01-01 13:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-31 22:44 [ISSUE] " removewingman
2023-12-31 22:49 ` classabbyamp
2023-12-31 22:54 ` [ISSUE] [CLOSED] " removewingman
2023-12-31 22:54 ` removewingman
2023-12-31 23:06 ` removewingman
2024-01-01  2:26 ` classabbyamp
2024-01-01 10:09 ` removewingman
2024-01-01 13:32 ` [ISSUE] [CLOSED] " Duncaen
2024-01-01 13:32 ` Duncaen [this message]
2024-01-01 14:41 ` classabbyamp

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=20240101133227.aT2lZOs3HB0SRE674IG3afQ02ZCLU1JX7dQTj_et2dk@z \
    --to=duncaen@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).