From: leetnc <leetnc@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [Package Request] OSMO
Date: Thu, 07 May 2020 00:09:20 +0200 [thread overview]
Message-ID: <20200506220920.h6YK89f413cRZK4TlwfIZ-Pb1lDrz-mXLNyvstIQr90@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21359@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
New comment by leetnc on void-packages repository
https://github.com/void-linux/void-packages/issues/21359#issuecomment-624917311
Comment:
I have stumbled into the trap of the build trying to re-compile gcc and
cups because the version has changed since I first did the "git clone....."
exercise for the 'void-linux' directory. Is there a convenient way to
update the templates (~/void-packages/srcpkgs) without cloning the whole
thing again and editing it for templates I added for osmo, etc. ? I may
not have the terminology quite right in my question.
On Tue, Apr 28, 2020 at 10:49 PM biopsin <notifications@github.com> wrote:
> Good to read! xbps-src is such a delight to use. If you get stuck in
> anyway, either search the templates here for hints or always ask the peeps
> on the wire.
> Still need to test against musl and pack libgringotts for the backup to
> function, but you are welcome to beat me to it :D .. (memo: add ical to
> defaults)
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/issues/21359#issuecomment-620962363>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AK2PA7HE4VS6WOOEL73QHNTRO6ITZANCNFSM4MRNV2LA>
> .
>
next prev parent reply other threads:[~2020-05-06 22:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 22:10 [ISSUE] " leetnc
2020-04-27 10:02 ` biopsin
2020-04-27 10:23 ` biopsin
2020-04-28 22:24 ` leetnc
2020-04-29 2:49 ` biopsin
2020-05-06 22:09 ` leetnc [this message]
2020-05-07 2:08 ` abenson
2020-05-07 2:09 ` abenson
2020-05-07 2:09 ` abenson
2020-05-07 2:13 ` abenson
2020-05-07 5:30 ` leetnc
2020-05-10 0:11 ` leetnc
2020-05-10 19:05 ` leetnc
2020-05-11 17:05 ` leetnc
2020-05-13 1:36 ` leetnc
2020-05-14 18:22 ` leetnc
2020-05-14 19:01 ` leetnc
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=20200506220920.h6YK89f413cRZK4TlwfIZ-Pb1lDrz-mXLNyvstIQr90@z \
--to=leetnc@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).