From: freddylist <freddylist@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: User template repositories?
Date: Thu, 13 Oct 2022 14:24:27 +0200 [thread overview]
Message-ID: <20221013122427.IiUBd6KiPDfVxH2REClvPgGDO-EpohG8PGdawE2-Plk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39900@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]
New comment by freddylist on void-packages repository
https://github.com/void-linux/void-packages/issues/39900#issuecomment-1277527085
Comment:
> This is not actionable and has been discussed before
I don't know if #19830 should count as a discussion, considering the author was speaking through a translator and was clearly upset by some brush with the Void Linux community...
> `void-packages` is by design a monorepo which comes with its advantages and limitations, hacking around them is not supported.
Sure, but it's still useful to have some semblance of user repositories, especially when you think of all the juicy new contributors that could come from these user repositories. I thought we might discuss some hacks for user repositories, even if they aren't "officially" supported.
For instance, after much contemplation, I came up with [this](https://github.com/freddylist/xbps-src-overlay-demo), which (ab)uses `overlayfs` to trick `xbps-src` into finding templates from multiple directories.
> Changing this would mean entirely changing the design of `xbps-src`.
It was mentioned in the other issue that supporting multiple `srcpkgs` dirs was "[the wrong way of handling the issue](https://github.com/void-linux/void-packages/issues/19830#issuecomment-595679246)" and that it would be "[hard to implement a way how to supply multiple directories](https://github.com/void-linux/void-packages/issues/19830#issuecomment-595695312)", but not *why*. Maybe there is a lot about package management I don't understand, but I don't see how it could be a bad idea to support multiple `srcpkgs` dirs. Just skimming through the `xbps-src` code I think it might be a couple dozen extra lines of Bash to implement multiple `srcpkgs` dirs in a non-breaking way.
Unless I am convinced otherwise or have grossly underestimated how hard it would be to implement, I can maybe have a draft version of `xbps-src` that supports multiple `srcpkgs` dirs, probably configured the same way my hack above is (symlinks in some `repos/` directory or something).
next prev parent reply other threads:[~2022-10-13 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 20:53 [ISSUE] " freddylist
2022-10-11 21:28 ` [ISSUE] [CLOSED] " paper42
2022-10-11 21:28 ` paper42
2022-10-11 21:28 ` paper42
2022-10-13 12:24 ` freddylist [this message]
2022-10-13 12:54 ` paper42
2022-10-13 12:55 ` paper42
2023-03-31 8:24 ` freddylist
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=20221013122427.IiUBd6KiPDfVxH2REClvPgGDO-EpohG8PGdawE2-Plk@z \
--to=freddylist@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).