From: DragonGhost7 <DragonGhost7@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Conky: update to 1.15.0, adopt.
Date: Sat, 05 Nov 2022 05:37:47 +0100 [thread overview]
Message-ID: <20221105043747.bUzmv3EgYXFBBRTHlt5e1eI9bGG9FUMFSaAA97WmpnM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40237@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
New comment by DragonGhost7 on void-packages repository
https://github.com/void-linux/void-packages/pull/40237#issuecomment-1304403011
Comment:
Update: Pulling the man pages is no problem, but since conky is built using cmake, configuring it and building 2 different packages by hand is incredibly difficult and results in incredibly long/complicated/not working templates. I believe it will be better to keep them as 2 different templates.
next prev parent reply other threads:[~2022-11-05 4:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 1:14 [PR PATCH] " DragonGhost7
2022-10-31 1:41 ` [PR PATCH] [Updated] " DragonGhost7
2022-10-31 2:30 ` DragonGhost7
2022-11-04 18:38 ` [PR REVIEW] " paper42
2022-11-04 21:20 ` DragonGhost7
2022-11-05 4:37 ` [PR PATCH] [Updated] " DragonGhost7
2022-11-05 4:37 ` DragonGhost7
2022-11-05 4:37 ` DragonGhost7 [this message]
2022-11-05 17:50 ` [PR REVIEW] " paper42
2022-11-05 17:50 ` paper42
2022-11-05 17:50 ` paper42
2022-11-05 18:10 ` DragonGhost7
2022-11-05 18:31 ` paper42
2022-11-05 19:19 ` DragonGhost7
2022-11-22 2:43 ` [PR PATCH] [Updated] " DragonGhost7
2022-11-22 4:54 ` DragonGhost7
2022-11-22 5:46 ` DragonGhost7
2022-11-22 5:51 ` DragonGhost7
2022-11-22 5:53 ` DragonGhost7
2022-11-22 6:03 ` DragonGhost7
2022-11-23 1:21 ` [PR PATCH] [Updated] " DragonGhost7
2023-02-21 2:02 ` github-actions
2023-03-07 2:07 ` [PR PATCH] [Closed]: " github-actions
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=20221105043747.bUzmv3EgYXFBBRTHlt5e1eI9bGG9FUMFSaAA97WmpnM@z \
--to=dragonghost7@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).