public inbox for [email protected]  

help / color / mirror / Atom feed

From: Pavel Raiskup <[email protected]>
To: [email protected]
Cc: Devrim Gündüz <[email protected]>
Cc: Alexandru Lazarev <[email protected]>
Cc: Adrian Klaver <[email protected]>
Cc: [email protected]
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/)
Date: Fri, 03 Aug 2018 10:30:51 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAL93h0GF0yo=WGHQjMDqyOJwcGQYOQKGpyGdhq8W22kDaReAoA@mail.gmail.com>
	<CAL93h0HxS3oGCJeF7kpWJnSfbSs1XjTf+SotmgJ+s+taP+6Cqw@mail.gmail.com>
	<[email protected]>

On Friday, August 3, 2018 8:08:55 AM CEST Devrim Gündüz 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 least 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 Linux
distributions.

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

Pavel

view thread (17+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  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/)
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox