public inbox for [email protected]
help / color / mirror / Atom feedFrom: Devrim Gündüz <[email protected]>
To: Daniel Farina <[email protected]>
To: Jason Petersen <[email protected]>
To: [email protected]
Subject: Re: Amazon Linux PGDG Repo?
Date: Tue, 10 Oct 2017 13:15:55 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAOPfGFizQpGSc3qAXgRXrbYF=c3EG3AYZJ3O3iH5MNo3mZMi0w@mail.gmail.com>
References: <[email protected]>
<[email protected]>
<CAOPfGFizQpGSc3qAXgRXrbYF=c3EG3AYZJ3O3iH5MNo3mZMi0w@mail.gmail.com>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-pkg-yum>
Hi,
On Mon, 2017-10-09 at 20:07 +0000, Daniel Farina wrote:
> As-is I'd probably continue to maintain a barely-good-enough fork of pgrpms
> to do my packages. Is there a better way?
How do you make those changes? Are they inside conditionals, like I did for
SLES, or did you just fork them? If they are inside conditionals, we can commit
them back to our repo as a first step -- at least it would save time for other
users.
The 2nd step would be having a community managed build server on Amazon, but
given that we recently added SLES 12 and RHEL 7 PPCLE support to our repo, I am
out of cycles to add a new platform. My community time at EDB is already 200%
booked.
Regards,
--
Devrim Gündüz
EnterpriseDB: https://www.enterprisedb.com
PostgreSQL Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachments:
[application/pgp-signature] signature.asc (833B, 2-signature.asc)
download
view thread (13+ 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]
Subject: Re: Amazon Linux PGDG Repo?
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