diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.gitignore diff --git a/.rh-postgresql13.metadata b/.rh-postgresql13.metadata new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.rh-postgresql13.metadata diff --git a/SOURCES/LICENSE b/SOURCES/LICENSE new file mode 100644 index 0000000..3912109 --- /dev/null +++ b/SOURCES/LICENSE @@ -0,0 +1,340 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) year name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. diff --git a/SOURCES/README b/SOURCES/README new file mode 100644 index 0000000..8076a19 --- /dev/null +++ b/SOURCES/README @@ -0,0 +1,40 @@ +Package %{scl_name} provides PostgreSQL database management system delivered as a Software +Collection. For more information about Software Collections, +see the scl(1) man page. By installing the %{scl_name} collection, +you will get the minimum working set of packages to have a working PostgreSQL database management system. + +Usage: scl enable %{scl} 'psql' + +Software Collections allow you to build and execute applications +which are not located in the filesystem root hierarchy, +but are stored in an alternative location, which is %{_scl_root} +in case of the %{scl_name} collection. + +PostgreSQL is an advanced Object-Relational database management system (DBMS). +The postgresql-server package contains the programs needed to create +and run a PostgreSQL server, which will in turn allow you to create +and maintain PostgreSQL databases. + +When you want to work with the %{scl_name} collection, use the scl +utility (see the scl(1) man page for usage) to enable the scl +environment. + +Configuration for the %{scl_name} software collection is located +under %{_sysconfdir}. + +Examples: +scl enable %{scl_name} 'command --arg' + Run a specific command with the argument --arg within the %{scl_name} + software collections environment. + +scl enable %{scl_name} 'psql' + Run psql from the %{scl_name} software collection. + +scl enable %{scl_name} bash + Run an interactive shell with the %{scl_name} software collection enabled. + +scl enable %{scl_name} 'man psql' + Show man pages for the psql command, which is a part of the + %{scl_name} software collection. + +Report bugs to . diff --git a/SPECS/rh-postgresql13.spec b/SPECS/rh-postgresql13.spec new file mode 100644 index 0000000..4c475ae --- /dev/null +++ b/SPECS/rh-postgresql13.spec @@ -0,0 +1,376 @@ +# Define SCL name +%{!?scl_name_prefix: %global scl_name_prefix rh-} +%{!?scl_name_base: %global scl_name_base postgresql} + +%{!?version_major: %global version_major 13} + +%{!?scl_name_version: %global scl_name_version %{version_major}} +%{!?scl: %global scl %{scl_name_prefix}%{scl_name_base}%{scl_name_version}} + +# Turn on new layout -- prefix for packages and location +# for config and variable files +# This must be before calling %%scl_package +%{!?nfsmountable: %global nfsmountable 1} + +# Define SCL macros +%{?scl_package:%scl_package %{scl}} + +# do not produce empty debuginfo package +%global debug_package %{nil} + +Summary: Package that installs %{scl} +Name: %{scl} +Version: 3.7 +Release: 1%{?dist} +License: GPLv2+ +Group: Applications/File +Source0: README +Source1: LICENSE +Requires: scl-utils +Requires: %{?scl_prefix}postgresql-server +BuildRequires: scl-utils-build help2man scl-utils-build-helpers + +%description +This is the main package for %{scl} Software Collection, which installs +necessary packages to use PostgreSQL %{version_major} server. +Software Collections allow to install more versions of the same +package by using alternative directory structure. +Install this package if you want to use PostgreSQL %{version_major} +server on your system. + + +%package runtime +Summary: Package that handles %{scl} Software Collection. +Group: Applications/File +Requires: scl-utils +Requires(post): policycoreutils-python libselinux-utils + +%description runtime +Package shipping essential scripts to work with %{scl} Software Collection. + + +%package build +Summary: Package shipping basic build configuration +Group: Applications/File +Requires: scl-utils-build scl-utils-build-helpers + +%description build +Package shipping essential configuration macros to build %{scl} Software +Collection or packages depending on %{scl} Software Collection. + + +%package scldevel +Summary: Package shipping development files for %{scl} + +%description scldevel +Package shipping development files, especially usefull for development of +packages depending on %{scl} Software Collection. + + +%if 0%{?scl_syspaths_metapackage:1} +%scl_syspaths_metapackage +Requires: %{?scl_prefix}postgresql-syspaths +Requires: %{?scl_prefix}postgresql-server-syspaths +Requires: %{?scl_prefix}postgresql-contrib-syspaths + +%scl_syspaths_metapackage_description +%endif + + +%prep +%setup -c -T + +%if 0%{!?fedora:1} && 0%{?rhel} <= 7 +%global _compat_scl 1 +%endif + +%global _scl_enable_script %{?_compat_scl:enable}%{!?_compat_scl:%{?scl}} + +%define _compat_scl_env_adjust() %{lua: \ +var = rpm.expand("%1") \ +if tonumber(rpm.expand('0%{?_compat_scl}'), 10) == 0 then \ + print(rpm.expand("prepend-path %1 %2")) \ +elseif var == "MANPATH" then \ + print(rpm.expand('export %1=%2:$%1')) \ +elseif var == "JAVACONFDIRS" then \ + print(rpm.expand('export %1=%2:${%1:-/etc/java}')) \ +elseif var == "XDG_CONFIG_DIRS" then \ + print(rpm.expand('export %1=%2:${%1:-/etc/xdg}')) \ +elseif var == "XDG_DATA_DIRS" then \ + print(rpm.expand('export %1=%2:${%1:-/usr/local/share:/usr/share}')) \ +else \ + print(rpm.expand('export %1=%2${%1:+:$%1}')) \ +end \ +} \ +%nil + +# This section generates README file from a template and creates man page +# from that file, expanding RPM macros in the template file. +cat <<'EOF' | tee README +%{expand:%(cat %{SOURCE0})} +EOF + +# copy the license file so %%files section sees it +cp %{SOURCE1} . + + +%build +# generate a helper script that will be used by help2man +cat <<'EOF' | tee h2m_helper +#!/bin/bash +[ "$1" == "--version" ] && echo "%{?scl_name} %{version} Software Collection" || cat README +EOF +chmod a+x h2m_helper + +# generate the man page +help2man -N --section 7 ./h2m_helper -o %{?scl_name}.7 + + +%install +%{?scl_install} + +# create and own dirs not covered by %%scl_install and %%scl_files +mkdir -p %{buildroot}%{_mandir}/man{1,7,8} + +# create enable scriptlet that sets correct environment for collection +cat <<\EOF | tee -a %{buildroot}%{?_scl_scripts}/%_scl_enable_script +%if 0%{!?_compat_scl:1} +#%%Module1.0 +prepend-path X_SCLS %{scl} + +%endif +# For binaries +%_compat_scl_env_adjust PATH %_bindir +# For header files +%_compat_scl_env_adjust CPATH %_includedir +# For libraries during build +%_compat_scl_env_adjust LIBRARY_PATH %_libdir +# For libraries during linking +%_compat_scl_env_adjust LD_LIBRARY_PATH %_libdir +# For man pages; empty field makes man to consider also standard path +%_compat_scl_env_adjust MANPATH %_mandir +# For Java Packages Tools to locate java.conf +%_compat_scl_env_adjust JAVACONFDIRS %_sysconfdir/java +# For pkg-config +%_compat_scl_env_adjust PKG_CONFIG_PATH %_libdir/pkgconfig +EOF + +# Automatically generate enable script when needed. +%{?scl_enable_script} + +cat << EOF | tee -a %{buildroot}%{_root_sysconfdir}/rpm/macros.%{scl_name_base}-scldevel +# macros to be used by packages depended on %scl collection +%%scl_%{scl_name_base} %{scl} +%%scl_prefix_%{scl_name_base} %{?scl_prefix} +EOF + +# install generated man page +mkdir -p %{buildroot}%{_mandir}/man7/ +install -m 644 %{?scl_name}.7 %{buildroot}%{_mandir}/man7/%{?scl_name}.7 + + +%post runtime +# Simple copy of context from system root to SCL root. +# In case new version needs some additional rules or context definition, +# it needs to be solved in base system. +# semanage does not have -e option in RHEL-5, so we would +# have to have its own policy for collection. +semanage fcontext -a -e / %{?_scl_root} >/dev/null 2>&1 || : +semanage fcontext -a -e %{_root_sysconfdir} %{_sysconfdir} >/dev/null 2>&1 || : +semanage fcontext -a -e %{_root_localstatedir} %{_localstatedir} >/dev/null 2>&1 || : + +selinuxenabled && load_policy || : +restorecon -R %{?_scl_root} >/dev/null 2>&1 || : +restorecon -R %{_sysconfdir} >/dev/null 2>&1 || : +restorecon -R %{_localstatedir} >/dev/null 2>&1 || : + + +%files + + +%files runtime -f filesystem +%doc README LICENSE +%{?scl_files} + + +%files build +%doc LICENSE +%{_root_sysconfdir}/rpm/macros.%{scl}-config + + +%files scldevel +%doc LICENSE +%{_root_sysconfdir}/rpm/macros.%{scl_name_base}-scldevel + + +%{?scl_syspaths_metapackage:%files syspaths} + + +%changelog +* Wed Dec 09 2020 Honza Horak - 3.7-1 +- Initial build of rh-postgresql13 + +* Fri Jul 26 2019 Honza Horak - 3.4-1 +- Convert to rh-postgresql12 + +* Tue Dec 12 2017 Pavel Raiskup - 3.1-1 +- sync with sclo-postgresql10 + +* Tue Dec 12 2017 Pavel Raiskup - 3.1-1 +- new collection rh-postgresql10 + +* Mon Sep 04 2017 Pavel Raiskup - 3.0-10 +- scldevel subpackage to depend on runtime subpackage +- don't set XDG_* variables, per rhbz#1464084 + +* Mon Jun 26 2017 Pavel Raiskup - 3.0-9 +- require contrib-syspaths by syspaths + +* Wed Jun 21 2017 Pavel Raiskup - 3.0-8 +- rebuild for description/summary changes in *-syspaths + +* Wed Jun 21 2017 Pavel Raiskup - 3.0-7 +- fix hack with _pkgdocdir; _pkgdocdir was defined every second build because we + defined the _pkgdocdir for ourselves + +* Wed Jun 21 2017 Pavel Raiskup - 3.0-6 +- add syspaths metapackage + +* Tue Jun 20 2017 Pavel Raiskup - 3.0-5 +- first build with scl_name_prefix 'rh-' + +* Tue Apr 18 2017 Pavel Raiskup - 3.0-4 +- add space after _compat_scl_env_adjust, the newline is not automatically + added on RHEL6 + +* Tue Apr 18 2017 Pavel Raiskup - 3.0-3 +- airier spec file + +* Wed Apr 12 2017 Pavel Raiskup - 3.0-2 +- scl-utils v2 fix + +* Thu Apr 06 2017 Pavel Raiskup - 3.0-1 +- bump version against scl 3 + +* Wed Jul 27 2016 Pavel Raiskup - 2.2-3 +- rebuild for s390x + +* Thu Feb 11 2016 Honza Horak - 2.2-2 +- Rebuild with newer scl-utils + +* Fri Jan 29 2016 Pavel Kajaba - 2.2-1 +- Release bump + +* Fri Mar 20 2015 Pavel Raiskup - 2.0-9 +- move the postgresql-ctl context definition to main package + +* Thu Mar 19 2015 Pavel Raiskup - 2.0-8 +- fix SELinux context on starting binaries once more + +* Wed Mar 18 2015 Pavel Raiskup - 2.0-7 +- merge rhel6 & rhel7 rh-postgresql94 branches + +* Wed Mar 18 2015 Pavel Raiskup - 2.0-6 +- fix SELinux context on starting binaries +- rebuild for scl-utils change (#1200057) + +* Wed Feb 18 2015 Honza Horak - 2.0-5 +- Remove NFS register feature for questionable usage for DBs + +* Thu Jan 29 2015 Jozef Mlich - 2.0-4 +- %{_unitdir} is available only in RHEL7 + +* Mon Jan 26 2015 Honza Horak - 2.0-3 +- Do not set selinux context scl root during scl register + +* Mon Jan 26 2015 Honza Horak - 2.0-2 +- Use cat for README expansion, rather than include macro + +* Sat Jan 17 2015 Honza Horak +- Apply many changes for new generation + +* Mon Oct 13 2014 Honza Horak - 1.1-21 +- Rebuild for s390x + Resolves: #1152432 + +* Mon Mar 31 2014 Honza Horak - 1.1-20 +- Fix path typo in README + Related: #1061456 + +* Wed Feb 19 2014 Jozef Mlich - 1.1-19 +- Release bump (and cherry pick from rhscl-1.1-postgresql92-rhel-7) + Resloves: #1061456 + +* Thu Feb 13 2014 Jozef Mlich - 1.1-18 +- Resolves: #1058611 (postgresql92-build needs to depend + on scl-utils-build) +- Add LICENSE, README and postgresql92.7 man page + Resloves: #1061456 + +* Wed Feb 12 2014 Honza Horak - 1.1-17 +- Add -scldevel subpackage + Resolves: #1063359 + +* Wed Dec 18 2013 Jozef Mlich 1-17 +- release bump + Resolves #1038693 + +* Tue Nov 26 2013 Jozef Mlich 1-16 +- By default, patch(1) creates backup files when chunks apply with offsets. + Turn that off to ensure such files don't get included in RPMs. + +* Fri Nov 22 2013 Honza Horak 1-15 +- Rename variable to match postgresql package + +* Mon Nov 18 2013 Jozef Mlich 1-14 +- release bump + +* Wed Oct 9 2013 Jozef Mlich 1-13 +- release bump to scl 1.1 + +* Wed May 22 2013 Honza Horak 1-12 +- Run semanage on whole root, BZ#956981 is fixed now +- Require semanage utility to be installed for -runtime package +- Fix MANPATH definition, colon in the end is correct (it means default) + Resolves: BZ#966382 + +* Fri May 3 2013 Honza Horak 1-11 +- Run semanage for all directories separately, since it has + problems with definition for whole root + +* Thu May 2 2013 Honza Horak 1-10 +- Handle context of the init script +- Add better descriptions for packages + +* Fri Apr 26 2013 Honza Horak 1-9 +- fix escaping in PATH variable definition + +* Mon Apr 8 2013 Honza Horak 1-8 +- Don't require policycoreutils-python in RHEL-5 or older +- Require postgresql-server from the collection as main package +- Build separately on all arches +- Fix Environment variables definition + +* Wed Feb 20 2013 Honza Horak 1-7 +- Use %%setup macro to create safer build environment + +* Fri Nov 09 2012 Honza Horak 1-6 +- rename spec file to correspond with package name + +* Thu Nov 08 2012 Honza Horak 1-5 +- Mark service-environment as a config file + +* Thu Oct 25 2012 Honza Horak 1-5 +- create service-environment file to hold information about all collections, + that should be enabled when service is starting +- added policycoreutils-python for semanage -e + +* Thu Oct 18 2012 Honza Horak 1-3 +- copy SELinux context from core mysql files + +* Wed Oct 03 2012 Honza Horak 1-2 +- update to postgresql-9.2 and rename to postgresql92 + +* Mon Mar 19 2012 Honza Horak 1-1 +- initial packaging +