Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n4o7J-0001Yl-TQ for pgsql-www@arkaria.postgresql.org; Tue, 04 Jan 2022 18:01:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n4o7I-0002Ui-He for pgsql-www@arkaria.postgresql.org; Tue, 04 Jan 2022 18:01:00 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n4o7I-0002UZ-Aj for pgsql-www@lists.postgresql.org; Tue, 04 Jan 2022 18:01:00 +0000 Received: from mail-yb1-xb2e.google.com ([2607:f8b0:4864:20::b2e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n4o7D-0008GQ-SW for pgsql-www@lists.postgresql.org; Tue, 04 Jan 2022 18:00:59 +0000 Received: by mail-yb1-xb2e.google.com with SMTP id w13so76530287ybs.13 for ; Tue, 04 Jan 2022 10:00:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=almalinux.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KXAcVFdQQl/jLNF24sdoIrVwtowXZzKK+25FhcJd2GM=; b=dutYv6iefD+LLjp/pzPQQsWcb6vgx3d1af0YxjnFiGuOeugBmt+l/1jux1gcXSvrxA wJyEGEeE3AAMPpekvqysYV/uj05yYLMkoE0GUHMVqcH6V/DG53BjxcXsGydYmMc8xhyl 2/MptepmUuInYYMVLW8xsJTztt7hMjMNL9G2eqU7ftzQEg8oeqhe24s/VvqiMAHOx9tb cC7EqdCw2kPRxX/0J5H3sT0JqZojXeSOwh1RcSOaSFDLpUsu1nwLEnHNNPlvpH4IdYLs 0qQ238iZY2hxGBe2O6M+jVfAFds71pm+DvCM+CLFoz5Uqx1m4HteqIAroRV/6I3B81AF eR9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KXAcVFdQQl/jLNF24sdoIrVwtowXZzKK+25FhcJd2GM=; b=vhdsr4A2STeCN7TtyBwCvLzMChomz4CIThwu1Zs8rYttW+gbElfn3hIjAUo3f4ZnKU yuu2qkFitJ6/OtSwQxEnbF2Tka/cHICPvurXuZihUnsmZSxNOJ0icEiDX53ncIYbi++q +IbeNW4GnWrdlrJkl1VmvpEaMqFeY0kwiAxX6k2J4YgDnox92GtvR12r27jbbfxpqULD dtHxtKVRISNAJlruC15SP4L6NVryQGZUCn38EnlidawbPPh459IoajDMEmybMpGx3CY4 rgbGPorbi7YalX/5IyG9xvSrCa7Pyldc5Z4i9WkqliPHrQQMy2d1kS/PfDfFLgJDFobv YbbA== X-Gm-Message-State: AOAM533uzswu7eg4ajx834JsU9geDVoGt2fLRvTKb+noWQ6f6eEiJ+A0 8n1ranRr2bN1Aieil/b36vaoqzkUtNHi+Ibvf3T1PfZGcllGQA== X-Google-Smtp-Source: ABdhPJwQDaxFa9/z9W7k9P3NZN2aYIeBu+rQ0GlAu8HNB41u1m3ZRugCrBslxiJsGaoFkzAVd4/hjjaDVKiDqZukYtc= X-Received: by 2002:a25:ef50:: with SMTP id w16mr43806001ybm.543.1641319253491; Tue, 04 Jan 2022 10:00:53 -0800 (PST) MIME-Version: 1.0 References: <8a29a8f8b9cb28ae010b77fcdbf709e70d1c9d56.camel@gunduz.org> <7efd7c0f73bedf467a038ae0f1e76a066b8cbf11.camel@gunduz.org> <9a1462c68c1c96f3d91ce5a5aae0473487ce2e31.camel@gunduz.org> <21cd5cf6865df80e0fb2b3a15dda90cb@postgresql.org> <5097ECAD-3AC4-4E1C-85B4-AE50F347E712@thebuild.com> In-Reply-To: <5097ECAD-3AC4-4E1C-85B4-AE50F347E712@thebuild.com> From: Jonathan Wright Date: Tue, 4 Jan 2022 12:00:37 -0600 Message-ID: Subject: Re: Add AlmaLinux as Specifically Supported Distro To: Christophe Pettus Cc: Justin Clift , =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= , "Jonathan S. Katz" , pgsql-www@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000011694505d4c56b88" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000011694505d4c56b88 Content-Type: text/plain; charset="UTF-8" On Tue, Jan 4, 2022 at 11:53 AM Christophe Pettus wrote: > > > > On Jan 4, 2022, at 09:49, Justin Clift wrote: > > Are we able to indicate on the download page that our CentOS RPMs > "should" > > work on AlmaLinux, though we haven't tested it ourselves? > > I think there would be a concern that if a community package doesn't work > on Alma, for whatever reason, we're implying that we will provide support > in some way. If we qualify it too much, it becomes "Alma exists" rather > than useful information for the downloader. Do you really want to exclude a large portion of the RHEL-clone userbase though? Oracle Linux is listed yet Alma has a much larger user base so I don't really understand the argument here. It also sounds odd to not want to support someone just because they're running Alma (or some other non-listed RHEL clone like say VZLinux). Since Rocky/Alma/Oracle/etc. are all binary compatible clones of RHEL any bug on one should exist on the others. It would benefit everyone overall to just treat them all the same instead of picking one favorite and in a sense excluding others. Building/testing is one thing but all of the clones that are indeed full clones should be treated the same from a community/support standpoint - for the benefit of users. Almost all other software and open source projects out there have taken this stance, even if they have a primary for building/testing. -- Jonathan Wright AlmaLinux Foundation Mattermost: chat --00000000000011694505d4c56b88 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Tue, Jan 4, 2022 at 1= 1:53 AM Christophe Pettus <xof@thebu= ild.com> wrote:


> On Jan 4, 2022, at 09:49, Justin Clift <justin@postgresql.org> wrote:
> Are we able to indicate on the download page that our CentOS RPMs &quo= t;should"
> work on AlmaLinux, though we haven't tested it ourselves?

I think there would be a concern that if a community package doesn't wo= rk on Alma, for whatever reason, we're implying that we will provide su= pport in some way.=C2=A0 If we qualify it too much, it becomes "Alma e= xists" rather than useful information for the downloader.
=

Do you really want to exclude a large portion of the RH= EL-clone userbase though?=C2=A0 Oracle Linux is listed yet Alma has a much = larger user base so I don't really understand the argument here.
<= div>
It also sounds odd to not want to support someone just b= ecause they're running Alma (or some other non-listed RHEL clone like s= ay VZLinux).=C2=A0 Since Rocky/Alma/Oracle/etc. are all binary compatible c= lones of RHEL any bug on one should exist on the others.=C2=A0 It would ben= efit everyone overall to just treat them all the same instead of picking on= e favorite and in a sense excluding others.=C2=A0 Building/testing is one t= hing but all of the clones that are indeed full clones should be treated th= e same from a community/support standpoint - for the benefit of users.=C2= =A0 Almost all other software and open source projects out there have taken= this stance, even if they have a primary for building/testing.
=

--
Jonathan Wright
AlmaLinux Foundation
Matter= most:=C2=A0chat
--00000000000011694505d4c56b88--