[Bigdata-commit] SF.net SVN: bigdata:[7589] branches/BIGDATA_RELEASE_1_3_0

[<tho...@us...>]

Revision: 7589
          http://bigdata.svn.sourceforge.net/bigdata/?rev=7589&view=rev
Author:   thompsonbry
Date:     2013-11-24 21:56:05 +0000 (Sun, 24 Nov 2013)
Log Message:
-----------
initial draft of an rpm install. this generates an rpm, but does not actually put anything into place when you do rpm -i yet.

Modified Paths:
--------------
    branches/BIGDATA_RELEASE_1_3_0/build.xml

Added Paths:
-----------
    branches/BIGDATA_RELEASE_1_3_0/src/resources/rpm/
    branches/BIGDATA_RELEASE_1_3_0/src/resources/rpm/bigdata.spec

Modified: branches/BIGDATA_RELEASE_1_3_0/build.xml
===================================================================
--- branches/BIGDATA_RELEASE_1_3_0/build.xml	2013-11-24 14:38:01 UTC (rev 7588)
+++ branches/BIGDATA_RELEASE_1_3_0/build.xml	2013-11-24 21:56:05 UTC (rev 7589)
@@ -1218,6 +1218,46 @@
 
     </target>
 
+    <!-- FIXME DEBUG and add 'depends="javadoc, stage" (should stage stage javadoc?)' -->
+    <!-- Note: can require 'rpm' and 'rpm-build. -->
+    <!-- TODO: We do not need both this and "deploy-artifact". -->
+    <target name="rpm" depends="prepare" description="Build RPM installer.">
+      <property name="rpm.dir" value="${build.dir}/rpm" />
+      <property name="stage.dir" value="dist" />
+      <mkdir dir="${rpm.dir}" />
+      <mkdir dir="${rpm.dir}/BUILD" />
+      <mkdir dir="${rpm.dir}/BUILDROOT" />
+      <mkdir dir="${rpm.dir}/RPMS" />
+      <mkdir dir="${rpm.dir}/SOURCES" />
+      <mkdir dir="${rpm.dir}/SPECS" />
+      <mkdir dir="${rpm.dir}/SRPMS" />
+      <copy file="${bigdata.dir}/src/resources/rpm/bigdata.spec" todir="${rpm.dir}/SPECS"/>
+      <!-- build version of tarball that includes the version number in the filename. -->
+      <copydir dest="${rpm.dir}/SOURCES/${version}" src="${stage.dir}/bigdata" />
+      <tar destfile="${rpm.dir}/SOURCES/${version}.tar.gz"
+           compression="gzip">
+        <tarfileset dir="${rpm.dir}/SOURCES">
+          <include name="${version}/**" />
+          <exclude name="${version}/bin/disco-tool" />
+          <exclude name="${version}/bin/pstart" />
+          <exclude name="${version}/bin/startHAServices" />
+        </tarfileset>
+        <!-- Add scripts separately, making them executable -->
+        <tarfileset dir="${rpm.dir}/SOURCES" filemode="755">
+          <include name="${version}/bin/disco-tool" />
+          <include name="${version}/bin/pstart" />
+          <include name="${version}/bin/startHAServices" />
+        </tarfileset>
+      </tar>
+<!--      <copy file="${bigdata.dir}/REL.${version}.tgz" tofile="${rpm.dir}/SOURCES/${version}.tar.gz"/> -->
+      <rpm
+        specFile="bigdata.spec"
+        topDir="ant-build/rpm"
+        cleanBuildDir="true"
+        failOnError="false"/>
+
+    </target>
+
     <target name="ant-install-prepare" depends="jar, bundle"
             description="Stage all files (src, lib, config, etc.) needed for ant based install.">
 

Added: branches/BIGDATA_RELEASE_1_3_0/src/resources/rpm/bigdata.spec
===================================================================
--- branches/BIGDATA_RELEASE_1_3_0/src/resources/rpm/bigdata.spec	                        (rev 0)
+++ branches/BIGDATA_RELEASE_1_3_0/src/resources/rpm/bigdata.spec	2013-11-24 21:56:05 UTC (rev 7589)
@@ -0,0 +1,46 @@
+Summary: bigdata RDF/graph database
+Name: bigdata
+Version: 1.2.3
+Release: 1
+License: GPLv2
+Group: Applications/Databases
+URL: http://www.bigdata.com/blog
+Source0: %{name}-%{version}.tar.gz
+BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root
+BuildArch: noarch
+
+Requires: java
+
+%description
+
+Bigdata is a horizontally-scaled, open-source architecture for indexed data with an emphasis on RDF capable of loading 1B triples in under one hour on a 15 node cluster.  Bigdata operates in both a single machine mode (Journal), highly available replication cluster mode (HAJournalServer), and a horizontally sharded cluster mode (BigdataFederation).  The Journal provides fast scalable ACID indexed storage for very large data sets, up to 50 billion triples / quads.  The HAJournalServer adds replication, online backup, horizontal scaling of query, and high availability.  The federation provides fast scalable shard-wise parallel indexed storage using dynamic sharding and shard-wise ACID updates and incremental cluster size growth.  Both platforms support fully concurrent readers with snapshot isolation.
+
+Distributed processing offers greater throughput but does not reduce query or update latency.  Choose the Journal when the anticipated scale and throughput requirements permit.  Choose the HAJournalServer for high availability and linear scaling in query throughput.  Choose the Federation when the administrative and machine overhead associated with operating a cluster is an acceptable tradeoff to have essentially unlimited data scaling and throughput.
+
+%package javadoc
+Summary:        API documentation for %{name}-%{version}
+
+%description javadoc
+API documentation for %{name}-%{version}
+
+%prep
+%setup -q
+
+%build
+
+%install
+rm -rf $RPM_BUILD_ROOT
+
+%clean
+rm -rf $RPM_BUILD_ROOT
+
+
+%files
+%defattr(-,root,root,-)
+%doc
+
+
+%changelog
+* Sun Nov 24 2013 EC2 Default User <ec2...@ip...ernal> - 
+- Initial build.
+

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.