| From: | Gražvydas Valeika <gvaleika(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Packaging of plpython |
| Date: | 2012-09-07 19:41:40 |
| Message-ID: | CAO6eJZpwFh3hyngqTdrmXwGkZhzjRZUf-jS2GwQ2eoMBf3cOdw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi all,
somebody please explain what is packaging policy of plpython. Now I see
plpython2u packaged in Fedora and RHEL repositories and plpython3u in
Windows installer by EnterpriseDB.
Why there is such difference and what is advertised way to keep DB servers
in Linux and Windows plpython compatible?
Difference in supported plpython versions for Linux/Windows adds
unnecessary difficulty.
Till now all I managed to google is advice to build required modules by
ourself.
What is the problem to provide both plpython2 and plpython3, or keep same
(2 or 3) plpython available by default on both platforms?
It seems to me, that this policy remains unchanged for 9.2.
Regards,
G.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2012-09-07 20:03:07 | Re: Packaging of plpython |
| Previous Message | Dmitriy Igrishin | 2012-09-07 19:36:25 | Re: Moving several databases into one database with several schemas |