From: Anachron <Anachron@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: public custom user repositories
Date: Fri, 06 Mar 2020 11:09:57 +0100 [thread overview]
Message-ID: <20200306100957.BvXQeE_MeW_4zbzdXisSD14udkKqC2rQBT9wx6YN9XE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19830@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
New comment by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/19830#issuecomment-595695312
Comment:
You can create your own repository with compiled packages and share it with someone else.
My suggestion: Make a new git repo, put your `srcpkgs` inside it and build those packages.
Then you host your own repository somewhere and add it to your `xbps` config using https://docs.voidlinux.org/xbps/repositories/custom.html
Edit: I briefly checked https://wiki.archlinux.org/index.php/Makepkg & https://git.archlinux.org/pacman.git/tree/scripts/makepkg.sh.in but I have not yet understood how this script works in detail yet.
Edit2: The problem is `xbps-src` is only aware of one source for pkg templates and that is https://github.com/void-linux/void-packages/blob/master/xbps-src#L532. It will be hard to implement a way how to supply multiple directories.
next prev parent reply other threads:[~2020-03-06 10:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 9:14 [ISSUE] " whoizit
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 [this message]
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=20200306100957.BvXQeE_MeW_4zbzdXisSD14udkKqC2rQBT9wx6YN9XE@z \
--to=anachron@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).