From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: postgresql14: update to 14.3.
Date: Fri, 20 May 2022 15:53:49 +0200 [thread overview]
Message-ID: <20220520135349.5R5z6vXLIzI88zBEN-cvcPyKr0DWFolMDfyGtSvrFD0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36770@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
New comment by TinfoilSubmarine on void-packages repository
https://github.com/void-linux/void-packages/pull/36770#issuecomment-1132928054
Comment:
> The problem is xbps can't replace regular file with alternative. The best thing possible I see is to make `postgresql` pure meta, keep the ugly `profile.sh` for all series waiting for everyone to update, and switch from profile to alternatives with postgresql 16.
This sounds good to me.
Just for clarification in regards to #35546: the `postgresql` template as written doesn't work because of the xbps limitation?
Do you want to also handle updating `postgresql14` in that, or should I keep this open?
next prev parent reply other threads:[~2022-05-20 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 18:25 [PR PATCH] postgresql14: update to 14.2 TinfoilSubmarine
2022-04-19 18:52 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-04-19 19:00 ` Chocimier
2022-04-19 19:14 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-04-19 19:14 ` TinfoilSubmarine
2022-05-07 21:49 ` Chocimier
2022-05-13 18:23 ` [PR REVIEW] " paper42
2022-05-16 15:56 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-05-20 13:53 ` TinfoilSubmarine [this message]
2022-07-04 20:05 ` postgresql14: update to 14.3 Chocimier
2022-07-04 20:05 ` [PR PATCH] [Closed]: " Chocimier
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=20220520135349.5R5z6vXLIzI88zBEN-cvcPyKr0DWFolMDfyGtSvrFD0@z \
--to=tinfoilsubmarine@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).