From: whoizit <whoizit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] public custom user repositories
Date: Fri, 06 Mar 2020 10:14:38 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19830@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
New issue by whoizit on void-packages repository
https://github.com/void-linux/void-packages/issues/19830
Description:
My friend and I got a lot of refusals to add templates to `void-packages` repo. My friend left the Void Linux community too early for this reason. I hate this situation too.
I did not find a guide on how to use my own public repositories. It looks like `xbps-src` is nailed to `void-packages`.
I want to create my own public repository (not fork `void-packages`). Also without `srcpkgs` dir inside repo. So that other users can easily find, use my templates, and also can add their own templates to my repository.
So my question is how to create my own `void-packages-extra` (or `void-extra-packages`) which is not a fork of `void-packages` or maybe it is worth thinking about taking out `./xbps-src` from the `void-packages` tree and make it available as package to public user repositories
I can’t lead a discussion about this because I don’t really speak English, it’s an online translator.
next reply other threads:[~2020-03-06 9:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 9:14 whoizit [this message]
2020-03-06 9:24 ` Anachron
2020-03-06 9:25 ` Anachron
2020-03-06 9:47 ` whoizit
2020-03-06 9:55 ` whoizit
2020-03-06 10:04 ` Anachron
2020-03-06 10:06 ` Anachron
2020-03-06 10:09 ` Anachron
2020-03-06 10:18 ` Piraty
2020-03-06 10:37 ` whoizit
2020-03-06 12:00 ` xtraeme
2020-03-06 12:00 ` [ISSUE] [CLOSED] " xtraeme
2020-03-06 12:00 ` xtraeme
2020-03-07 9:14 ` whoizit
2020-03-07 14:08 ` Anachron
2020-03-10 5:58 ` fosslinux
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-19830@inbox.vuxu.org \
--to=whoizit@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).