[med-svn] r1893 - trunk/packages/mgltools

Mon May 19 12:26:30 UTC 2008

Author: smoe-guest
Date: 2008-05-19 12:26:29 +0000 (Mon, 19 May 2008)
New Revision: 1893

Modified:
   trunk/packages/mgltools/BUILD
   trunk/packages/mgltools/README
Log:
Continued descriptions.


Modified: trunk/packages/mgltools/BUILD
===================================================================

--- trunk/packages/mgltools/BUILD	2008-05-19 10:29:16 UTC (rev 1892)
+++ trunk/packages/mgltools/BUILD	2008-05-19 12:26:29 UTC (rev 1893)
@@ -1,4 +1,14 @@
+MGLtools for Debian - build instructions
+========================================
 
+Contents: 
+
+	1. How to build from upstream CVS
+	2. How to build from upstream tar file
+
+1. How to build from upstream CVS
+---------------------------------
+
 The sources are made available on mgltools.scripps.edu. When deciding to download the latest from CVS, then perform as described here.
 Create a new directory, I used "mgltools-cvs" and cd to it.
 
@@ -65,3 +75,77 @@
 	done
 
 The relative path of the build-area may differ on your system. It can be set in .svn/deb-layout as buildArea=../../build-area
+
+
+2. How to build from upstream tar file
+--------------------------------------
+
+The major difference to the CVS distribution is the ready provisioning
+of gzipped tar files for each of the python modules. Also, you have a
+certain confidence in having downloaded the appropriate set of packages
+in a coherent version.
+
+Upstream has kept the .cvs directories in their source distribution
+to help with the provisioning of patches. This is against the policy
+of Debian but has been kept in the current version that was uploaded
+to the experimental section of Debian.
+
+To build the debian packages, the following approach is suggested, execute
+the commands listed below in a bash shell.
+
+
+bash <<EOPREPARATION
+
+# specify version for what you are packaging
+# (these instructions are possibly outdated :/ )
+VERSION=1.5.1
+
+# Stay in the current directory and download the upstream
+# source code ... or move or symbolically link that file to this
+# directory if you have downloaded it already
+wget http://mgltools.scripps.edu/downloads/tars/releases/REL$(VERSION)/mgltools_source_$(VERSION).tar.gz
+
+# unpack it
+tar xzvf mgltools_source_$(VERSION).tar.gz
+
+# prepare folder with tar files
+[ ! -d tarfiles ] && mkdir tarfiles
+cd tarfiles
+
+rm -rf "*.orig.tar.gz"
+
+# Create properly formatted readme files
+for i in  `ls ../mgltools_source_$VERSION/MGLPACKS/*.tar.gz`
+do
+  n=`basename $i |tr A-Z a-z | sed -e "s/-$VERSION/_$VERSION.orig/"`
+  ln -s $i $n || echo "Could not link $i to $n"
+done
+
+EOPREPARATION
+
+At this stage, you can use svn-buildpackage in each of the 
+*/trunk subdirectories to prepare the Debian package that
+would be required for the mgltools. The dependencies for
+the compilation of the packages are already set in
+the */trunk/debian/control files. The dependencies for
+executing the python modules are far stronger - and most may
+not have been determined yet!
+
+It would be appreciated if you could spare the time to help with
+augmenting the description of the individual packages. Feel free
+to ask for commit provileges for the Debian-Med alioth packages.
+
+To inspect the upstream sources is not ultimately required. It is however
+helpful to compare the Python setup scripts with its description with
+the descriptions given in debian/control. You may decide to move to
+mgltools_source_$(VERSION)/MGLPACKS and execute
+
+  for i in *.tar.gz; do tar xzvf $i; done
+
+
+
+
+
+Comments please send to 
+
+ -- Steffen <moeller at debian.org>  Mon, 19 May 2008 11:45:26 +0200

Modified: trunk/packages/mgltools/README
===================================================================
--- trunk/packages/mgltools/README	2008-05-19 10:29:16 UTC (rev 1892)
+++ trunk/packages/mgltools/README	2008-05-19 12:26:29 UTC (rev 1893)
@@ -18,10 +18,10 @@
 The AutoDockToolkit is part of the MLGTools and to some do sound
 more familiar than the MGLTools as a whole.  Hence, I cannot
 tell at the moment how exactly the MGLTools will make it into
-Debian or how I should dissect the upstream sources properly.
-To have the packages flocking together in this subdirectory seemed
-like a reasonable approach to me. Just tell me if you have some
-better ideas.
+Debian or how the upstream sources should be dissected properly.
+To have the packages flocking together in this subdirectory seemes
+like a reasonable first approach. Please inform Steffen of
+better ideas that appear to you.
 
 The package is in a semi-usable stage by now. Upstream's source
 tar file can be downloaded from mgltools.scripps.edu. The tar files
@@ -30,9 +30,11 @@
 All packages should compile just fine, except for opengltk which
 needs a line in /usr/include/GL/gl.h changed which is described
 just here http://mgltools.scripps.edu/downloads/instructions/1.5.0-source.
+The latest version was 1.5.1 should have this fixed which is available on
+http://mgltools.scripps.edu/downloads/tars/releases/REL1.5.1/mgltools_source_1.5.1.tar.gz.
 
-I personally am not overly happy yet with the stability of the 
-molecular graphics display. Yet I need to figure out if the official
-version behaves any better.
+Earlier versions had issues with the stability of the 
+molecular graphics display. This is considered to have improved,
+please inform upstream of remaining issues.
 
-Steffen				 Thu 20. Dez 20:12:06 CET 2007
+ -- Steffen <moeller at debian.org>  Mon, 19 May 2008 11:34:56 +0200


