Github messages for voidlinux
 help / color / mirror / Atom feed
From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: postgresql-client (and thus postgres) is missing in xbps-alternatives
Date: Tue, 04 Apr 2023 18:00:53 +0200	[thread overview]
Message-ID: <20230404160053.5wb8OKxShzAf5wNC9ybI2TRLpq8Y4jxEDS2halZKoK4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43259@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/issues/43259#issuecomment-1496230769

Comment:
Cześć,

That's expected but can be changed with 16 series.

Postgresql 9.6 occupied /usr/bin/psql and was removed only a year ago. While it was still in repo, newer series were installed in /usr/lib, as xbps can't yet transactionally replace executable with an alternative. In order for new series to be accessible, profile scripts adding them to PATH exist. Shadowing of newer series by older ones is a mistake, but not too bad.

This setup is still in place to give people time to pull in now-meta postgresql package. As 16 will enter repos well over a year after removal of 9.6, it will be good time to introduce alternatives.

For server, separate services are in place, so this is not a problem.

Another question is why do you want to switch client (continuously, afaiu?), when other options are to remove old package and relogin; call by absolute path; or manipulate PATH in shell rc file?

  reply	other threads:[~2023-04-04 16:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 14:53 [ISSUE] " soanvig
2023-04-04 16:00 ` Chocimier [this message]
2023-04-05  9:24 ` soanvig
2023-04-05  9:25 ` soanvig
2023-04-05  9:26 ` soanvig
2023-07-05  2:06 ` github-actions
2023-07-05  9:06 ` [ISSUE] [CLOSED] " soanvig

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=20230404160053.5wb8OKxShzAf5wNC9ybI2TRLpq8Y4jxEDS2halZKoK4@z \
    --to=chocimier@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).