update thredds, enabled binstar build

thredds/.binstar.yml

@@ -0,0 +1,78 @@
+
+## The package attribure specifies a binstar package namespace to build the package to. 
+## This can be specified here or on the command line
+package: thredds
+
+## You can also specify the account to upload to,
+## you must be an admin of that account, this 
+## defaults to your user account
+user: birdhouse 
+
+#===============================================================================
+# Build Matrix Options
+# Thes options may be a single item, a list or empty
+# The resulting number of builds is [platform * engine * env] 
+#===============================================================================
+
+## The platforms to build on.
+## platform defaults to linux-64 
+# platform: 
+#  - linux-64
+#  - linux-32
+## The engine are the inital conda packages you want to run with 
+# engine:
+#  - python=2
+#  - python=3
+## The env param is an environment variable list 
+# engine:
+#  - MY_ENV=A CC=gcc
+#  - MY_ENV=B
+
+#===============================================================================
+# Scrip options
+# Thes options may be broken out into the before_script, script and after_script
+# or not, that is up to you 
+#===============================================================================
+
+## Run before the script
+before_script:
+  - conda update -n root conda-build
+  - conda config --add channels https://conda.binstar.org/birdhouse
+
+## Put your main computations here!  
+script:
+  - conda build .
+## This will run after the script regardless of the result of script
+## BINSTAR_BUILD_RESULT=[succcess|failure] 
+# after_script:
+#   - echo "The build was a $BINSTAR_BUILD_RESULT" | tee artifact1.txt
+## This will be run only after a successfull build
+# after_success:
+#   - echo "after_success!"
+## This will be run only after a build failure
+# after_failure:
+#   - echo "after_failure!"
+
+#===============================================================================
+# Build Results
+# Build results are split into two categories: artifacts and targets
+# You may omit either key and stiff have a successfull build
+# They may be a string, list and contain any bash glob
+#===============================================================================
+
+## Build Artifacts: upload anything you want!
+## Your build artifacts will be put into the website
+## http://artifacts.build.binstar.info/USERNAME/PACKGE_NAME/BUILD_NO
+## You can store all logs or any derived data here
+## Remember, the site http://artifacts.build.binstar.info is NOT secure and does not
+## require a user to log in to view
+# build_artifacts:
+#   - *.log
+
+## Build Targets: Upload these files to your binstar package
+## build targets may be a list of files (globs allows) to upload
+## The special build targets 'conda' and 'pypi' may be used to 
+## upload conda builds  
+## e.g. conda is an alias for /opt/anaconda/conda-bld/<os-arch>/*.tar.bz2
+build_targets:
+  - conda

thredds/meta.yaml

@@ -1,12 +1,12 @@
 
 package:
     name: thredds
-    version: 4.3.22
+    version: 4.3.23
 
 source:
     fn: thredds.war 
-    url: ftp://ftp.unidata.ucar.edu/pub/thredds/4.3/4.3.22/thredds.war
-    md5: 0a863f6e3a4e040d0861e84ce508b07e
+    url: ftp://ftp.unidata.ucar.edu/pub/thredds/4.3/4.3.23/thredds.war
+    md5: d032618c3e9acfa860795e2f10a36f86
 
 build:
     number: 0