diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.gitignore diff --git a/.rh-mongodb32.metadata b/.rh-mongodb32.metadata new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.rh-mongodb32.metadata diff --git a/README.md b/README.md deleted file mode 100644 index 98f42b4..0000000 --- a/README.md +++ /dev/null @@ -1,4 +0,0 @@ -The master branch has no content - -Look at the c7 branch if you are working with CentOS-7, or the c4/c5/c6 branch for CentOS-4, 5 or 6 -If you find this file in a distro specific branch, it means that no content has been checked in yet diff --git a/SOURCES/LICENSE b/SOURCES/LICENSE new file mode 100644 index 0000000..d159169 --- /dev/null +++ b/SOURCES/LICENSE @@ -0,0 +1,339 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc., + 51 Franklin Street, 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 Lesser 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 Street, 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 Lesser General +Public License instead of this License. diff --git a/SOURCES/README b/SOURCES/README new file mode 100644 index 0000000..f07f470 --- /dev/null +++ b/SOURCES/README @@ -0,0 +1,41 @@ +Package %{scl_name} provides MongoDB server 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 +MongoDB server. + +Usage: scl enable %{scl} 'mongod' + +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. + +This package provides the mongod server daemon and the mongos +sharding server daemon software, default configuration files and +init scripts. + +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} 'mongod' + Run mongod from the %{scl_name} software collection. + +scl enable %{scl_name} 'bash' + Run an interactive shell wherein the %{scl_name} software collection + is enabled. + +scl enable %{scl_name} 'man mongod' + Show man pages for the mongod command, which is a part of the + %{scl_name} software collection. + +Report bugs to . diff --git a/SPECS/rh-mongodb32.spec b/SPECS/rh-mongodb32.spec new file mode 100644 index 0000000..ffaf122 --- /dev/null +++ b/SPECS/rh-mongodb32.spec @@ -0,0 +1,437 @@ +# Define SCL name +%{!?scl_name_prefix: %global scl_name_prefix rh-} +%{!?scl_name_base: %global scl_name_base mongodb} +%{!?version_major: %global version_major 3} +%{!?version_minor: %global version_minor 2} +%{!?scl_name_version: %global scl_name_version %{version_major}%{version_minor}} +%{!?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 (https://bugzilla.redhat.com/show_bug.cgi?id=1061439#c2) +%global debug_package %{nil} + +# Convert SCL name into uppercase including - to _ conversion +%if 0%{?scl:1} +%global scl_upper %{lua:print(string.upper(string.gsub(rpm.expand("%{scl}"), "-", "_")))} +%endif + +Summary: Package that installs %{scl} +Name: %{scl} +Version: 2.2 +Release: 8%{?dist} +License: GPLv2+ +Group: Applications/File +# template of man page with RPM macros to be expanded +Source0: README +# mongodb license +Source1: LICENSE +Requires: scl-utils +Requires: %{?scl_prefix}mongodb-server +BuildRequires: scl-utils-build, help2man +BuildRequires: rh-java-common-javapackages-tools +BuildRequires: rh-maven33-scldevel +BuildRequires: golang + +%description +This is the main package for %{scl} Software Collection, which installs +necessary packages to use MongoDB %{version_major}.%{version_minor} 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 MongoDB %{version_major}.%{version_minor} +server on your system + +%package runtime +Summary: Package that handles %{scl} Software Collection. +Group: Applications/File +Requires: scl-utils +Requires: /usr/bin/scl_source +# Those two java common requires are for build-classpath et. al. +# to work. See RHBZ#1129287 +Requires: %{?scl_prefix_java_common}runtime +Requires: %{?scl_prefix_java_common}javapackages-tools +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 +Requires: scl-utils-build +Requires: %{name}-scldevel = %{version} +Requires: %{scl_prefix}scldevel +Group: Applications/File + +%description build +Package shipping essential configuration macros to build +%scl Software Collection. + +%package scldevel +Summary: Package shipping development files for %{scl}. +Group: Applications/File +Requires: %{name}-runtime = %{version} +#Requires: %{scl_prefix_maven}-scldevel +Requires: rh-maven33-scldevel + +%description scldevel +Development files for %{scl} (useful e.g. for hierarchical collection +building with transitive dependencies). + +%prep +%setup -c -T + +# java.conf +cat <configuration.xml + + + + + %{?_scl_root}/usr/share/maven-metadata + + + %{?_scl_root} + + + + ${ROOT_NOSLASH}/usr/share/maven-metadata + + + + resolve-%{scl} + compound + + ${ROOT_NOSLASH} + %{scl} + + + + base-resolve + + + + + resolve-rh-maven33 + compound + + opt/rh/rh-maven33/root + rh-maven33 + + + + base-resolve + + + + + resolve + compound + + + + resolve-local + resolve-%{?scl} + resolve-%{?scl_maven} + + + + + install + compound + + ${ROOT_NOSLASH} + %{scl} + + + + base-install + + + + + +EOF + +#=====================# +# Javapackages config # +#=====================# +cat <> %{buildroot}%{_scl_scripts}/service-environment << EOF +# Services are started in a fresh environment without any influence of user's +# environment (like environment variable values). As a consequence, +# information of all enabled collections will be lost during service start up. +# If user needs to run a service under any software collection enabled, this +# collection has to be written into %{scl_upper}_SCLS_ENABLED variable in +# /opt/rh/sclname/service-environment. +%{scl_upper}_SCLS_ENABLED='%{scl}' +EOF + +install -d -m 755 %{buildroot}%{_sysconfdir}/java +install -p -m 644 java.conf %{buildroot}%{_sysconfdir}/java/ +install -p -m 644 javapackages-config.json %{buildroot}%{_sysconfdir}/java/ + +install -d -m 755 %{buildroot}%{_sysconfdir}/xdg/xmvn +install -p -m 644 configuration.xml %{buildroot}%{_sysconfdir}/xdg/xmvn/ + +# Create java/maven directories so that they'll get properly owned. +# These are listed in the scl_files macro. See also: RHBZ#1057169 +install -d -m 755 %{buildroot}%{_javadir} +install -d -m 755 %{buildroot}%{_prefix}/lib/java +install -d -m 755 %{buildroot}%{_javadocdir} +install -d -m 755 %{buildroot}%{_mavenpomdir} +install -d -m 755 %{buildroot}%{_datadir}/maven-effective-poms +install -d -m 755 %{buildroot}%{_mavendepmapfragdir} + +# install generated man page +install -d -m 755 %{buildroot}%{_mandir}/man7 +install -p -m 644 %{?scl_name}.7 %{buildroot}%{_mandir}/man7/ + +# create directory for license +install -d -m 755 %{buildroot}%{_licensedir} + +# create directory for golang code +install -d -m 755 %{buildroot}%{_datadir}/gocode +install -d -m 755 %{buildroot}%{_datadir}/gocode/src + +# generate rpm macros file for depended collections +cat << EOF | tee -a %{buildroot}%{_root_sysconfdir}/rpm/macros.%{scl_name_base}-scldevel +%%scl_%{scl_name_base} %{?scl} +%%scl_prefix_%{scl_name_base} %{?scl_prefix} +EOF + + +%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 by changing selinux-policy. +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 + +%if 0%{?rhel} >= 7 || 0%{?fedora} >= 15 +%files runtime -f filesystem +%license LICENSE +%dir %attr(0755, root, root) %{_sysconfdir}/java/ +%dir %attr(0755, root, root) %{_licensedir}/ +%dir %attr(0755, root, root) %{_javadir} +%dir %attr(0755, root, root) %{_mavenpomdir} +%else +%files runtime +%doc LICENSE +%endif +%doc README +%{?scl_files} +%config(noreplace) %{_scl_scripts}/service-environment +%config(noreplace) %{_sysconfdir}/java/java.conf +%config(noreplace) %{_sysconfdir}/xdg/xmvn/configuration.xml +%config(noreplace) %{_sysconfdir}/java/javapackages-config.json +%{_mandir}/man7/%{?scl_name}.* +# Directories for golang code (requrements of mongo-tools) +%dir %{_datadir}/gocode +%dir %{_datadir}/gocode/src +%dir %{_javadocdir} + +%files build +%doc LICENSE +%{_root_sysconfdir}/rpm/macros.%{scl}-config + +%files scldevel +%doc LICENSE +%{_root_sysconfdir}/rpm/macros.%{scl_name_base}-scldevel + +%changelog +* Thu Apr 21 2016 Marek Skalicky - 2.2-8 +- Fixed syntax in man page + Resolves: #1219517 + +* Thu Feb 18 2016 Marek Skalicky - 2.2-7 +- Fixed xmvn configuration + +* Tue Feb 16 2016 Marek Skalicky - 2.2-6 +- Add javadocdir ownership + +* Mon Feb 8 2016 Marek Skalicky - 2.2-5 +- Fix ownership of golang src directory + +* Mon Feb 8 2016 Marek Skalicky - 2.2-4 +- Now using rh-maven33 SCL + +* Wed Jan 27 2016 Marek Skalicky - 2.2-3 +- Added GOPATH to able to use a golang packages in this SCL + +* Mon Jan 11 2016 Marek Skalicky - 2.2-2 +- Fixed PYTHONPATH to include also pythonarch directory + +* Thu Mar 19 2015 Marek Skalicky - 2.0-19 +- Fixed java and maven directory ownership + +* Wed Mar 18 2015 Marek Skalicky - 2.0-18 +- Use license instead of doc (used by mongodb) +- Fixed rhel7 runtime {_licensedir} directory ownership + +* Mon Mar 2 2015 Marek Skalicky - 2.0-17 +- Fixed rhel7 runtime {_sysconfdir}/java/ directory ownership + +* Fri Feb 27 2015 Honza Horak - 2.0-16 +- Remove NFS register feature for questionable usage for DBs + +* Mon Jan 26 2015 Honza Horak - 2.0-15 +- Fix upper format of scl name + +* Mon Jan 26 2015 Honza Horak - 2.0-14 +- Create correct directory under register.content + +* Mon Jan 26 2015 Marek Skalicky - 2.0-13 +- Fixed runtime subpackage file section + +* Mon Jan 26 2015 Honza Horak - 2.0-12 +- Do not set selinux context scl root during scl register + +* Mon Jan 26 2015 Honza Horak - 2.0-11 +- Use cat for README expansion, rather than include macro + +* Fri Jan 23 2015 Marek Skalicky - 2.0-10 +- Added service-environment into mongodb package +- Fixed runtime directory ownership + +* Thu Jan 22 2015 Marek Skalicky - 2.0-9 +- Merged origin/rhscl-2.0-rh-mongodb26-rhel-7 (2.0-9) + +* Wed Jan 21 2015 Marek Skalicky - 2.0-8 +- Moved SCL python27 dependency into rh-mongodb26-mongodb + +* Tue Jan 20 2015 Marek Skalicky - 2.0-7 +- Added SCL python27 dependency + +* Sat Jan 17 2015 Honza Horak - 2.0-6 +- Initial register implementation + +* Wed Jan 14 2015 Severin Gehwolf - 2.0-5 +- Update java/maven configuration for thermostat consumption. + +* Tue Jan 13 2015 Honza Horak - 2.0-4 +- Implement some new scl-utils features and use more scl macros + +* Mon Nov 24 2014 Marek Skalicky 2.0-3 +- Modified files section to correctly uninstall SCL root + +* Tue Nov 18 2014 Marek Skalicky 2.0-2 +- Changed and cleaned up requirements + +* Fri Nov 14 2014 Marek Skalicky 2.0-1 +- added SCL v8 dependency +- changed version for SCL 2.0 + +* Fri Nov 07 2014 Marek Skalicky 1-2 +- removed SCL v8 dependency + +* Thu Oct 30 2014 Marek Skalicky 1-1 +- initial packaging (based on mongodb24 SCL) +