Changeset 81b369bb in sasview for build_tools

Timestamp:

Feb 14, 2015 8:14:50 AM (10 years ago)

Author:

Peter Parker

Branches:

master, ESS_GUI, ESS_GUI_Docs, ESS_GUI_batch_fitting, ESS_GUI_bumps_abstraction, ESS_GUI_iss1116, ESS_GUI_iss879, ESS_GUI_iss959, ESS_GUI_opencl, ESS_GUI_ordering, ESS_GUI_sync_sascalc, costrafo411, magnetic_scatt, release-4.1.1, release-4.1.2, release-4.2.2, release_4.0.1, ticket-1009, ticket-1094-headless, ticket-1242-2d-resolution, ticket-1243, ticket-1249, ticket885, unittest-saveload

Children:

981a1d4

Parents:

34f113ad

Message:

Convert to actual GitHub? markdown.

File:

• build_tools/conda/README.md (modified) (3 diffs)

build_tools/conda/README.md

@@ -1 @@
-= Conda Recipes =
+# Conda Recipes
 
 Here we store the recipes for building conda packages of the dependencies of SasView.  These are dependencies that unforunately do not come pre-bundled with Anaconda.
 
-== Creating a Recipe ==
+# Creating a Recipe
 
 An easy way to get started with a recipe is to use the skeleton command that comes with conda, which looks for all the information it needs on PyPi (of course, this will only work if the module exists on PyPi...):
 
-{{{
+```
 conda skeleton pypi package_name
-}}}
+```
 
 This automatically chooses the most recent version up on PyPi.  You may specify an older version as follows:
 
-{{{
+```
 conda skeleton pypi package_name --version 1.0.9
-}}}
+```
 
 If you run `conda skeleton` from this directory, then the recipes will go into the right place. 
@@ -25 +25 @@
 * Sometimes downloading the package from PyPi is problematic.  You may see something like the following:
 
-  {{{
+  ```
   Error: Could not open 'C:\\TempAnaconda\\conda-bld\\src_cache\\showfiles.php?group_id=15583.part' for writing ([Errno 22] invalid mode ('wb') or filename: 'C:\\TempAnaconda\\conda-bld\\src_cache\\showfiles.php?group_id=15583.part').
-  }}}
+  ```
 
-  If so, the {{{source:}}} values in meta.yaml are pointing to external urls that are not direct links to the downloads (in the case above, a .php link).  Change  {{{fn:}}} and {{{url:}}} from {{{http://sourceforge.net/project/showfiles.php?group_id=15583}}} or similar to an actual link to a .zip of .tar.gz.  Remember to add a correct {{{mdf:}}} property so that future users have their downloads checked.
+  If so, the `source:` values in meta.yaml are pointing to external urls that are not direct links to the downloads (in the case above, a .php link).  Change  `fn:` and `url:` from `http://sourceforge.net/project/showfiles.php?group_id=15583` or similar to an actual link to a .zip of .tar.gz.  Remember to add a correct `mdf:` property so that future users have their downloads checked.
 
 * I once tried to use recipes generated with older versions of conda and ran into problems.  Your options here are either to hack away at the recipe until it works, or just re-generate the recipe with skeleton.
 
-== Building a Conda Package and Uploading to Binstar ==
+# Building a Conda Package and Uploading to Binstar
 
-{{{
+```
 conda build bumps\
-}}}
+```
 
-{{{
+```
 TEST END: bumps-0.7.5.4-py27_0
 # If you want to upload this package to binstar.org later, type:
@@ -47 +47 @@
 # To have conda build upload to binstar automatically, use
 # $ conda config --set binstar_upload yes
-}}}
+```