From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: New PostgreSQL categories
Date: Mon, 28 Oct 2024 16:21:14 +0100 [thread overview]
Message-ID: <54de2ebf62c2e2510e59a7b914dc10907a9f8657.camel@gentoo.org> (raw)
In-Reply-To: <7eb6a37e-bd6a-434b-b97a-21eacdbed981@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
On Mon, 2024-10-28 at 14:49 +0100, Patrick Lauer wrote:
> I've just returned from the pgconf.eu conference, and this has motivated
> me to try to improve the packaging situation for all things PostgreSQL
> in Gentoo.
>
> Right now everything just goes into dev-db/ category. That's not
> inherently wrong, but it feels a bit overloaded to me. So I'd like to
> add two new categories. I'm relatively indifferent about the naming,
> good suggestions welcome, but locally I ended up naming them "pg-tools"
> and "pg-extensions". As the name suggests, one category is tools around
> PostgreSQL, and the other is extensions. (Or maybe it makes sense to put
> all of it into a dev-postgres category?)
That's inconsistently long with how we name categories. "-plugins"
would probably be more consistent too.
> - extensions, new packages:
> […]
Are you actually going to maintain all these new packages, or just dump
and effectively abandon them, as usual?
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2024-10-28 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 13:49 [gentoo-dev] RFC: New PostgreSQL categories Patrick Lauer
2024-10-28 13:57 ` Miroslav Šulc (fordfrog)
2024-10-28 13:59 ` Volkmar W. Pogatzki
2024-10-28 14:08 ` Agostino Sarubbo
2024-10-28 14:10 ` Azamat Hackimov
2024-10-28 15:21 ` Michał Górny [this message]
2024-10-28 17:07 ` Patrick Lauer
2024-10-28 19:15 ` Ulrich Müller
2024-10-29 22:22 ` Haelwenn (lanodan) Monnier
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=54de2ebf62c2e2510e59a7b914dc10907a9f8657.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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