From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: element-desktop: update to 1.10.7.
Date: Tue, 03 May 2022 09:51:00 +0200 [thread overview]
Message-ID: <20220503075100.vC4EiR_8cMfDiTiTapANRmt7efKXl429Szj1QfmncGc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35336@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/35336#issuecomment-1115826103
Comment:
> Can we use create_wrksrc to make sure everything gets cleaned up?
I've looked into this for a bit, but it's not quite as trivial as I had hoped. It makes fiddeling with the patches a bit more difficult. I can't find a way to dynamically generate the patch args for the two different extracted tarballs, as `${PATCHESDIR}` is read only and writing it next to the `.patch` file in the `${XBPS_BUILDDIR}` doesn't seem to have any effect. Any idea how to handle this?
next prev parent reply other threads:[~2022-05-03 7:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 19:37 [PR PATCH] element-desktop: update to 1.10.0 jcgruenhage
2022-02-01 6:57 ` [PR PATCH] [Updated] " jcgruenhage
2022-02-02 6:17 ` jcgruenhage
2022-02-12 11:26 ` jcgruenhage
2022-03-26 20:44 ` jcgruenhage
2022-03-30 5:43 ` element-desktop: update to 1.10.7 notramo
2022-03-30 5:44 ` notramo
2022-03-30 13:42 ` [PR PATCH] [Updated] " jcgruenhage
2022-05-03 7:05 ` jcgruenhage
2022-05-03 7:23 ` jcgruenhage
2022-05-03 7:51 ` jcgruenhage [this message]
2022-06-10 17:12 ` jcgruenhage
2022-06-10 17:39 ` classabbyamp
2022-06-10 17:41 ` classabbyamp
2022-06-10 18:30 ` [PR PATCH] [Updated] " jcgruenhage
2022-06-10 19:14 ` [PR PATCH] [Merged]: element-desktop: update to 1.10.14 Johnnynator
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=20220503075100.vC4EiR_8cMfDiTiTapANRmt7efKXl429Szj1QfmncGc@z \
--to=jcgruenhage@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).