From: Jason Stephenson Date: Tue, 26 Mar 2013 15:01:50 +0000 (-0400) Subject: Add new dependency on libbz2-dev(el). X-Git-Tag: sprint4-merge-nov22~3103^2~7 X-Git-Url: https://old-git.evergreen-ils.org/?a=commitdiff_plain;h=78e19fd3f4c8baa6d003ee230d18bf0c34e9f00b;p=working%2FEvergreen.git Add new dependency on libbz2-dev(el). Our own mar tools add a build dependency on libbz2. The easiest way to make sure this is there seems to be to install libbz2-dev(el). Also, update the release notes to reflect the new dependency. Signed-off-by: Jason Stephenson Signed-off-by: Ben Shum --- diff --git a/Open-ILS/src/extras/Makefile.install b/Open-ILS/src/extras/Makefile.install index a49ea6a646..fc46d62774 100644 --- a/Open-ILS/src/extras/Makefile.install +++ b/Open-ILS/src/extras/Makefile.install @@ -87,7 +87,8 @@ DEBS = \ libuniversal-require-perl\ libnet-ip-perl\ liblocale-maketext-lexicon-perl\ - libunix-syslog-perl + libunix-syslog-perl\ + libbz2-dev # Debian Lenny and Ubuntu Intrepid bundle recent versions of yaz EXTRA_DEBS = \ @@ -159,7 +160,8 @@ FEDORA_RPMS = \ readline-devel \ tcp_wrappers-devel \ wget \ - yaz + yaz \ + libbz2-devel # Note: B:O:AuthorizeNet 3.21 fails with https://rt.cpan.org/Public/Bug/Display.html?id=55172 # Should be fixed in 3.22 diff --git a/docs/RELEASE_NOTES_NEXT/Administration/new-updates-tools.txt b/docs/RELEASE_NOTES_NEXT/Administration/new-updates-tools.txt index a65b488561..7c94024976 100644 --- a/docs/RELEASE_NOTES_NEXT/Administration/new-updates-tools.txt +++ b/docs/RELEASE_NOTES_NEXT/Administration/new-updates-tools.txt @@ -14,12 +14,15 @@ Evergreen during the installation or upgrade process. The make_updates.sh script that is run when you tell Evergreen to make the staff client updates has been modified to use the new tools. -These tools introduce no new dependencies on building or running -Evergreen. +These tools introduce a dependency on libbz2. This is often only +available when installing the libbz2-dev or libbz2-devel packages. +Thus this branch introduces a new depency on the development packages +for libbz2 in Evergreen. Nothing in the user facing behavior of building updates changes with these tools. They are drop-in replacements for the previous tools and -you don't even need to know that they are there. +other than the new dependency on libbz2, you don't even need to know +that they are there. These tools were added to Evergreen to be an aid in portability to operating systems other than Linux. They also remove a dependency on