Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fmmTb-00012R-Ru for pgsql-pkg-yum@arkaria.postgresql.org; Mon, 06 Aug 2018 20:51:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fmmTa-0003KC-FO for pgsql-pkg-yum@arkaria.postgresql.org; Mon, 06 Aug 2018 20:51:38 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fmmTa-0003K3-6W for pgsql-pkg-yum@lists.postgresql.org; Mon, 06 Aug 2018 20:51:38 +0000 Received: from mail-lf1-x141.google.com ([2a00:1450:4864:20::141]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fmmTW-0003IV-UM for pgsql-pkg-yum@lists.postgresql.org; Mon, 06 Aug 2018 20:51:36 +0000 Received: by mail-lf1-x141.google.com with SMTP id v22-v6so10045794lfe.8 for ; Mon, 06 Aug 2018 13:51:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xeVYa79FSybR0kq0eUIZByteDVDQXKNgdkl7cbgSO10=; b=rMtcR0lt3cJ/h4MvSs2abNdPpQwozzjJIUX9n3sc4xZX/ooYJxtzG1N2NyFvqHNerD SbCpjj3KA086Ffn5gjP4U13fLf2s2swxCA+sLxNzqkTmQP1OCKmLR1+VafmCY5CclYYt PYrF/RstS8jqKSSo1yw9xshW+ec5b+nHGdI4aStbGRL5TORta9rRxjpXJuRGTeW/SQGg hjQUWuEtQTQx6R4A5dbTend/9dKQzbE6RNfvm1z0C1NSsM0M4NY6tcGHD8ulClimy1Io f9T2jT4jadmQSx6qtzYHYD31LAutDeKGlOB1fWYo09iLs6kpU2sycceWzOqmPCiVDyTy /dpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xeVYa79FSybR0kq0eUIZByteDVDQXKNgdkl7cbgSO10=; b=i0LMxycz3qPK96kH5AvIetQu9J8uAfzqVPbDNn8piMrfiMRf6HDlooh0hV4Lx6q6+X h797OBXFkOwSAceVNj61v8//YO4Dda7Drtkz7OAdkcklnOWDORVu5QfwDJw4DXrIT8s5 T9E44IvW4aw0gz0ng80ZHMPa7VQI/P9aISRBRm2M28UWObtgD3eXx307KTJaZuWyiDtj h7ctS+NOY1koOC2n13QRE8ldSoyxz0x/kEsp+Q8r8smNLYy9f1U1zfK5N8HscQZucYz5 XQsEMy/xiYHLCng+X/5a/m5rSJ5rBfnejDhE9O6C2leomW3FHEBnwco2UqSk6Ijj1e4T migQ== X-Gm-Message-State: AOUpUlE1iOUbucxkkxcGGCdPPFy/f+aaeaXfch00TQL0fSFprKEb03vJ nXkl1evUIwFKcKjZLHfcOYA1Kal3S+MFU3ZwVxM= X-Google-Smtp-Source: AAOMgpdG1KVdi3gAFjKboy9tew0NExkhCLWNQkroj1+ZBq+Jpx3lmKvVu/r6/u9Cu1V/YPLbfFOXQ71d12g+rKlMbog= X-Received: by 2002:a19:be54:: with SMTP id o81-v6mr12073586lff.31.1533588693256; Mon, 06 Aug 2018 13:51:33 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:c40c:0:0:0:0:0 with HTTP; Mon, 6 Aug 2018 13:51:32 -0700 (PDT) In-Reply-To: <2836136.ULnCWUqcGg@nb.usersys.redhat.com> References: <1cdedaf455c4f326f31b103ab805d48da9914cb7.camel@gunduz.org> <2836136.ULnCWUqcGg@nb.usersys.redhat.com> From: Alexandru Lazarev Date: Mon, 6 Aug 2018 23:51:32 +0300 Message-ID: Subject: Re: Who and How is responsible for released installations packages and 3rd party packs? (e.g. on https://yum.postgresql.org/9.6/redhat/rhel-7.3-x86_64/) To: Pavel Raiskup , pgsql-pkg-yum@lists.postgresql.org, =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= , myon@debian.org Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="0000000000004b13350572ca7108" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000004b13350572ca7108 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks all for responses. Let me ask other dummy question: plv8 RPMs were built by PostgreSQL Community for different OSes, or by those OSes vendors/community (e.f. RedHat/Debian, etc)? And the same question about postgresql-server install packages themselves (RPMs, debs, etc) Thanks in advance On Fri, Aug 3, 2018 at 11:30 AM, Pavel Raiskup wrote: > On Friday, August 3, 2018 8:08:55 AM CEST Devrim G=C3=BCnd=C3=BCz wrote: > > On Thu, 2018-08-02 at 16:26 +0300, Alexandru Lazarev wrote: > > > What about 3rd party libraries like plv8 - Who and How (based on whic= h > > > criteria, which versions) build RPM and upload them there? > > > > Latest versions of PL/v8 does not build on RHEL/Fedora anymore, at leas= t > from > > the package build point of view. > > Yes, packaging of plv8 is pretty complicated. If one decided to ship RPM > package with plv8, it would mean maintenance of whole v8 language - which > is incredibly complicated (incompatible changes all the time, backporting > security fixes, etc.). > > That's the reason why plv8 (and even v8 runtime) becomes dropped from Lin= ux > distributions. > > [1] https://github.com/plv8/plv8/issues/281 > > Pavel > > > > --0000000000004b13350572ca7108 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks all for responses.

Let me ask oth= er dummy question:
plv8 RPMs were built by PostgreSQL Commun= ity for different OSes, or by those OSes vendors/community (e.f. RedHat/Deb= ian, etc)?
And the same question about postgresql-server inst= all packages themselves (RPMs, debs, etc)

Thanks i= n advance


On Fri,= Aug 3, 2018 at 11:30 AM, Pavel Raiskup <praiskup@redhat.com> wrote:
On Friday, Au= gust 3, 2018 8:08:55 AM CEST Devrim G=C3=BCnd=C3=BCz wrote:
> On Thu, 2018-08-02 at 16:26 +0300, Alexandru Lazarev wrote:
> > What about 3rd party libraries like plv8 - Who and How (based on = which
> > criteria, which versions) build RPM and upload them there?
>
> Latest versions of PL/v8 does not build on RHEL/Fedora anymore, at lea= st from
> the package build point of view.

Yes, packaging of plv8 is pretty complicated.=C2=A0 If one decided t= o ship RPM
package with plv8, it would mean maintenance of whole v8 language - which is incredibly complicated (incompatible changes all the time, backporting security fixes, etc.).

That's the reason why plv8 (and even v8 runtime) becomes dropped from L= inux
distributions.

[1] https://github.com/plv8/plv8/issues/281

Pavel




--0000000000004b13350572ca7108--